On Tue, 29 Oct 2002, Poul-Henning Kamp wrote:
> I don't think we need to go overboard, but we are in the run{up,down}
> to a release now, so some extra testing would be nice.
I think this point may not have gotten the attention it deserves. Being so
close to a major release, why are we changing m
Juli Mallett wrote:
> * De: Poul-Henning Kamp <[EMAIL PROTECTED]> [ Data: 2002-10-29 ]
> > Having a set of regression tests for make under src/tools/regression
> > would be really cool as well.
>
> I agree with you 100%. It'd be nice if people with esoteric-but-valid
> build systems using our mak
Juli Mallett wrote:
> > Please test make(1) changes on "make release" in the future.
>
> The standard metric has been 'make buildworld' I thought? Anyway, try
> with revision 1.2 of var_modify.c, that should do it.
>
> Realistically, to prevent any sort of breakage to make(1), we should
> test m
* De: Poul-Henning Kamp <[EMAIL PROTECTED]> [ Data: 2002-10-29 ]
[ Subjecte: Re: make(1) broken! ]
> >Realistically, to prevent any sort of breakage to make(1), we should
> >test make(1) by building every port that does not USE_GMAKE, and do
> >release, and do cro
In message <[EMAIL PROTECTED]>, Juli Mallett writes:
>> Please test make(1) changes on "make release" in the future.
>
>The standard metric has been 'make buildworld' I thought? Anyway, try
>with revision 1.2 of var_modify.c, that should do it.
There are a lot of weird make targets which are onl
* De: Poul-Henning Kamp <[EMAIL PROTECTED]> [ Data: 2002-10-29 ]
[ Subjecte: make(1) broken! ]
>
> I've wasted most of my morning on locating why make release was broken.
>
> The answer is that make(1) does not do variable substitutions right
> now,
I've wasted most of my morning on locating why make release was broken.
The answer is that make(1) does not do variable substitutions right
now, and in particular the line
CATDIR= ${MANDIR:H:S/$/\/cat/}
in bsd.man.mk produces the breaking bogosity. Notice that the "man" seems
t
