Based on PR port-powerpc/40421 from Wojciech Galazka,
with misc tweaks by me.
Note sysinst part is not pulled because there is
no supported storage device yet on this port.
* Don't change METALOG in place while creating METALOG.sanitised in the
sanitise_METALOG target. This makes it easier to manually inspect
METALOG to find the order in which lines were added during a build.
* Add a clean_METALOG target, to be invoked from src/Makefile early in
the build, to prevent unbounded growth of METALOG during multiple
MKUPDATE builds.
* Remove the old hack of incorporating etc/mtree/NetBSD.dist into
METALOG.sanitised. It was needed only during a short transition
period when people might have done MKUPDATE builds starting from
existing DESTDIR and OBJDIR trees that had been created before
revision 1.317 of src/etc/Makefile.
* Since etc/mtree/NetBSD.dist is no longer added, there's will not
be any "optional" lines, so there's no need to filter them from
METALOG.sanitised.
* There's no need for two different METALOG.unpriv and
METALOG.sanitised.unpriv variables; combine them into a single
METALOG.unpriv variable whose value is "-M ${METALOG}.sanitised".
* Reorder some lines in the Makefile, to bring related targets,
variables and comments together.
first, mount root and run the various disk providers. Add swap and
check the remaining file systems after that.
This breaks the dependency cycle for lvm, which needs writeable /dev.
Depend on rndctl in cgd.
- retire libXaw8
- remote Xprint support from xmore
- bump libXaw7 to major 10 so that "libXaw.so" gets a new SONAME, and
make it the "libXaw" used.
XXX: this probably should be pulled up to netbsd-5, which is why i have
XXX: separated it out from the general Xprint removal
non-compat equivalent files, to stop amd64/sparc64 builds with MKxxx=no
options from failing because files in the DESTDIR are missing from the
METALOG.
amd64 builds, now, with several MKxxx=no options set. sparc64 probably
needs some more work.
FWIW, join(1) saved me some manual labor as I copied keywords from
non-compat to compat files:
1 Collect the files that are missing from the DESTDIR into
compat-i386.files
2 Replicate the first column of compat-i386.files. Remove i386/ from
the first column.
3 sort -k 1,1 distrib/sets/lists/comp/{md.amd64,mi,shl.*}
distrib/sets/lists/base/{md.amd64,mi,module.amd64,module.mi,shl.elf,sh
l.mi} | join -1 1 -2 1 -o '2.2 1.3' - compat-i386.files >
compat-i386.keywords
4 Process distrib/lists/{base,comp}/md.amd64 with join -1 1 -2 1 -o '1.1
1.2 1.3,2.2' -a1 - compat-i386.keywords
when installing hard links. They have no effect except when using a
metalog, in which case the information is added to the metalog. In
the future, these variables may be replaced by a method for explicitly
recording hard links in a metadata log.
Also change a few things that called ${INSTALL_LINK} without going
through bsd.links.mk.
Reviewed by perry and joerg. This should fix PR 24457 and PR 41155.
- add HAVE_UFS2_BOOT define on ports which have UFS2 capable loader
- reject UFS2 for root file system on ports !HAVE_UFS2_BOOT
- add a MI function to get bootxx name from root file system type
per MD defines and remove md_bootxx_name() from arch/i386/md.c,
so that alpha can use bootxx_ffsv2 for UFS2 as well as x86
Tested on i386 and alpha with FFSv1 and FFSv2, and also
tested on vax (on simh) for !HAVE_UFS2_BOOT case.
de translation is provided by martin@.
No objection on tech-install, and "move forward with it" from perry@.
XXX1: not tested on all ports, more ports might/could have UFS2 root support
XXX2: no es, fr, and pl translations, even en message should be improved
XXX3: alpha has a fixed en message without MSG
"DEBUG:", or else regpkg assumes that they are error messages. Make the
verbose messages printed by the list_set_files function follow that
convention. Fixes PR 41077 from Lloyd Parkes.
/usr/X11R7/lib/libXaw.so.6
/usr/X11R7/lib/libXaw.so.7
/usr/X11R7/lib/libXaw.so.8
Note that there is still some use of the "LIBOLD" variables in the
Makefiles associated with PKG* variables that I don't understand.
Discussed with mrg and martin
METALOG could have different order due to install(1) race
on parallel builds, and mtree(8) doesn't sort files.
Should fix inconsistent shared sets among builds as seen in
/pub/NetBSD-daily/netbsd-5/200904010000Z/shared/ and
/pub/NetBSD-daily/netbsd-5/200904010002Z/shared/ dirs.
Okay'ed by snj@.
