9152e1c5a7
The tested targets are the followgin ones: * tools * distribution * sets * release The remaining NetBSD targets have not been disabled nor tested *at all*. Try them at your own risk, they may reboot the earth. For all compliant Makefiles, objects and generated files are put in MAKEOBJDIR, which means you can now keep objects between two branch switching. Same for DESTDIR, please refer to build.sh options. Regarding new or modifications of Makefiles a few things: * Read share/mk/bsd.README * If you add a subdirectory, add a Makefile in it, and have it called by the parent through the SUBDIR variable. * Do not add arbitrary inclusion which crosses to another branch of the hierarchy; If you can't do without it, put a comment on why. If possible, do not use inclusion at all. * Use as much as possible the infrastructure, it is here to make life easier, do not fight it. Sets and package are now used to track files. We have one set called "minix", composed of one package called "minix-sys"
20 lines
836 B
Plaintext
20 lines
836 B
Plaintext
TODO list for system packages
|
|
=============================
|
|
|
|
+ commit Alan Barrett's mods from PR 22514 for system package building
|
|
from build.sh
|
|
+ decide whether to keep a separate system package database of
|
|
metadata, and, if so, where to keep it
|
|
+ if using separate database, add a flag to support this to pkg_*
|
|
+ add syspkg support to sysinst
|
|
+ add pkg_install utilities (and necessary sub-utilities) to
|
|
the crunched install tools
|
|
+ fix sysinst to use them
|
|
+ need a tool to create meta-packages
|
|
+ base-bind meta-pkg created from base-bind-root,
|
|
base-bind-bin and base-bind-example
|
|
+ base meta-pkg created from base-* meta-pkgs
|
|
+ bundle packages into tar files (`pkgsets'per src/distrib/syspkg/notes)
|
|
+ meta-pkg content entirely derivable from pkg names (base-*, base-bind-*)
|
|
+ add system packages to the release ISOs
|