Subject: Re: checkflist error codes
To: Greywolf <greywolf@starwolf.com>
From: Frederick Bruckman <fredb@immanent.net>
List: current-users
Date: 11/05/2003 14:01:43
On Wed, 5 Nov 2003, Greywolf wrote:

> Thus spake Frederick Bruckman ("FB> ") sometime Today...
>
> FB> On Wed, 5 Nov 2003, Greywolf wrote:
> FB>
> FB> > Example:  I want to build a distribution with no /lib, /libexec or
> FB> > /rescue, and a statically-linked root. Or I might want to build a pure
> FB> > static distribution.  Or I might want to build a distribution that uses
> FB> > compressed manual pages.  Or I might want to build a distribution which
> FB> > will install nicely onto an embedded installation.

> FB> The build could be a little smarter, and set ${NOPOSTINSTALL} if
> FB> various MK* options are set to "no". For yourself, can't you simply
> FB> set ${NOPOSTINSTALL}?

> Certainly no affront meant, but this is like trying to place a band-aid
> over a shotgun wound.  There should be several flist files conditionally
> tossed into the final mix, and checkflist should run against that, rather
> than running against the Whole Big Default Picture.

Well, since we don't support making sets with non-default options,
there doesn't seem to be much point at all in running checkflist. Nor
would it make much sense to try to support building custom sets, as
sysinstall wouldn't know how to deal with them.

Frederick