Date: Tue, 29 Oct 2002 05:08:54 -0800 From: Juli Mallett <jmallett@FreeBSD.org> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: current@FreeBSD.ORG Subject: Re: make(1) broken! Message-ID: <20021029050854.A903@FreeBSD.org> In-Reply-To: <90384.1035896204@critter.freebsd.dk>; from phk@critter.freebsd.dk on Tue, Oct 29, 2002 at 01:56:44PM %2B0100 References: <20021029041633.A96819@FreeBSD.org> <90384.1035896204@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
* De: Poul-Henning Kamp <phk@critter.freebsd.dk> [ 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 cross-release. Or just not modify it, except for
> >bugfixes, which should be tested as above.
>
> 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.
>
> 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 make(1) could submit some edge cases to make
up said tests. I've got a few simple ones, none of which test much on
the "real world behaviour relied upon" side.
At the very least, a suite of "FreeBSD make mistake" tests would be good
for anyone who decides they want to take up the ever-touted merge-with-otherbsd
job.
juli.
--
Juli Mallett <jmallett@FreeBSD.org> | FreeBSD: The Power To Serve
Will break world for fulltime employment. | finger jmallett@FreeBSD.org
http://people.FreeBSD.org/~jmallett/ | Support my FreeBSD hacking!
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021029050854.A903>