On Sun, Jun 19, 2005 at 04:10:00PM +0100, Robert Watson wrote: > XXX I liked that it seemed easy to do incremental rebuilds with NanoBSD, > but found I had to do a fair amount of manually deleting intermediate > targets to get it to work. One thing I found that really didn't work > was that if you install any third party packages, you have to blow away > the DESTDIR install tree or when you re-build, the packages conflict and > abort the image creation. Posted so someone else will save the time I spent figuring this out: I've added pkgs to CUSTOMIZE in make.conf, created the Pkg subdirectory, and stuck a whole bunch of packages in there. Some of these packages are dependent on others: i.e., dnswalk requires perl and assorted p5-Digest-blah packages. Of course, I have the dependency packages in the Pkg directory. The nanobsd build stops with "*** error code 4". The Customize/pkg script tries to add each package in order. It installs the dependencies when installing the package, just as you would expect. When it gets to the dependency package, it generates an error even though the packages have been installed. When you have X packages that have been previously installed, you get error code X. The fix is pretty complicated. After the build stops, do # mv _.cs.tmp _.cs # make Overall, though, I have to say that nanobsd sucks far less than any of the previous options I had. ==ml -- Michael W. Lucas mwlucas_at_FreeBSD.org, mwlucas_at_BlackHelicopters.org http://www.BlackHelicopters.org/~mwlucas/ "The cloak of anonymity protects me from the nuisance of caring." -Non SequiturReceived on Mon Jun 20 2005 - 16:23:14 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:37 UTC