Date: Wed, 14 Jul 2004 00:46:16 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Jon Disnard <diz@linuxpowered.com> Cc: current@freebsd.org Subject: Re: CVSUP and 5.2.1 RELEASE Message-ID: <27752.1089758776@critter.freebsd.dk> In-Reply-To: Your message of "Tue, 13 Jul 2004 17:40:26 CDT." <40F464DA.4030501@linuxpowered.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <40F464DA.4030501@linuxpowered.com>, Jon Disnard writes: >>The correct solution is the add whatever it takes to make the world >>target fail if it is unsafe. >> >So possibly a system to parse UPDATING, or whatever, for ABI changes and >then halting the installworld stages of the world target? Well, maybe we need a different criteria for bumping __FreeBSD_version or maybe we need a parallel ABI version number, but parsing UPDATING would be a hack. >That seems good and bad, because sometimes people checkin without any >documentation, and this idea would absolutely require anything with a >potential to cause hazard to be documented with (or before) the >associated checkin. Are all the commiters diligent enough to do that? Is >there some other way we can have this idea of a "smart make world" that >acknowledges the case of lazy documentation? I think that if we make it a rule that __FreeBSD_version be bumped if make world without a kernel update would be unsafe would be followed. -- 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?27752.1089758776>