Re: Making install CDs contain the full sets
Alan Barrett <[email protected]>
| Newsgroups | gmane.os.netbsd.devel.installation |
|---|---|
| Message-ID | <[email protected]> |
On Tue, 12 Aug 2014, Martin Husemann wrote:
> I wonder if build.sh should be able to deal with an invocation
> like "build.sh release iso-image" and enforce the (now
> necessarry) variant "build.sh release sets iso-image".
"release" includes "sets", but build.sh doesn't know that; it's
encoded in rules in src/Makefile and src/etc/Makefile.
> Actually I'd like "build.sh iso-image" to automagically expand
> to that.
No, I don't think you would; at least, not in the simple form you
expressed it. If you have already done "build.sh release", I
don't think you'd want "build.sh iso-image" to repeat all that
work.
build.sh does not have dependency management, except in some
very small ways such as always building the make wrapper before
anything else. If you need multiple steps to be performed, you
need to request them explicitly. At present, build.sh doesn't
know that iso-image won't work if you haven't already built a
release, and it doesn't know whether or not you have already built
a release.
I have contemplated adding a little more dependency management,
perhaps keeping a bunch of ".done_${operation}" marker files
somewhere, but I am not keen to go very far down the path of
reimplementing "make" in build.sh.
--apb (Alan Barrett)