Date: Tue, 29 Oct 2002 13:56:44 +0100 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Juli Mallett <jmallett@FreeBSD.ORG> Cc: current@FreeBSD.ORG Subject: Re: make(1) broken! Message-ID: <90384.1035896204@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 29 Oct 2002 04:16:34 PST." <20021029041633.A96819@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20021029041633.A96819@FreeBSD.org>, 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 only used for
installworld, distribute and release, so for something as omnibuggable
as make(1), I would prefer if you used make release.
>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.
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
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?90384.1035896204>