Re: Rework of nrelease

[joerg@xxxxxxxxxxxxxxxxx]

On Wed, Dec 07, 2005 at 11:04:36AM -0800, Matthew Dillon wrote:
> 
>     I don't want to make the nrelease build dependant on a
>     binary packages directory sitting on packages.stura.uni-rostock.de.

It isn't. The situation hasn't changed at all compared to e.g. the
installer packages before.  Consider it a temporary mean until the list
of packages is finished.  The files can be moved e.g. to leaf or crater
for the release.

>     Also, the 'check' target and the other convenience targets (to
>     fetch and configure pkgsrc and/or fetch required packages) need
>     to remain intact.  I don't want programmers to be forced to use
>     obscure -D<LABEL> names to build common targets.  The check target

There are two possible situations. If you are building snapshots etc,
having knobs for /etc/make.conf is IMO the simpler solution. If you
want to customize the setup, knobs are much better, since it doesn't
need twenty different targets for all the interesting combinations.
This leaves out the question of the default (with or without installer),
but it is consistent with the rest of the framework.

>     in particular is very important as it prevents the user from having
>     to run through an entire buildworld before being told that something
>     is missing.

The check target can't be implemented correctly without also hard-coding
the package list. That's something I want to avoid. Adhoc checks are
possible like whether the bootstrap kit exists, but that doesn't cover
all cases of course.

Joerg