thor0505%comcast.net@localhost writes: > For the time being, I have decided to create a custom shell script in > the spirit of etcmanage, after looking over BUILD-NetBSD; perhaps an > INSTALL-NETBSD custom shell script will follow. I do a large amount of > cross-building (my NetBSD compiling box is an Ubuntu machine), and I'm > not sure how easy it is to use use etcmanage on a Linux host, where > the only access to the target NetBSD's /etc files would either be > SSHFS, SMB, FTP, or NFS. So using BUILD-NetBSD should be independent of running etcmanage to update the etc files on a system. It probably works on Linux. > This is probably overkill, but this m4 script generates a number of > variables which can be used to start a ./build.sh session where > directories are separated based on target. It current supports > rebuilding from scratch and updating after "cvs update/git pull". The > script also supports choosing MAKECONF and the kernel to be compiled. > The script assumes the tools directory already exists, but this is > okay, since the same tools directory can be used for all possible > targets. m4 is used to reduce the chance I make a mistake on a > per-architecture basis. > > https://gist.github.com/cr1901/07b8e6810caedc31fe7c > > Hopefully this is useful to somebody... and since it's a gist, it can be > forked as well :P. Thanks for posting. I just run 'release' so tools get built if not already, and that doesn't hurt much time wise.
Attachment:
pgpJ1cdEXdzYK.pgp
Description: PGP signature