From owner-freebsd-current@FreeBSD.ORG Tue Jul 13 22:40:37 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E899316A4CE for ; Tue, 13 Jul 2004 22:40:37 +0000 (GMT) Received: from rivendell.linuxpowered.com (rivendell.linuxpowered.com [67.18.110.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id B37DF43D2D for ; Tue, 13 Jul 2004 22:40:37 +0000 (GMT) (envelope-from diz@linuxpowered.com) Received: from localhost (localhost [127.0.0.1]) by rivendell.linuxpowered.com (Postfix) with ESMTP id 53CA6980004; Tue, 13 Jul 2004 17:36:53 -0500 (CDT) Received: from rivendell.linuxpowered.com ([127.0.0.1]) by localhost (rivendell [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 28594-09; Tue, 13 Jul 2004 17:36:50 -0500 (CDT) Received: from linuxpowered.com (txirvcom-itnfw01.verizon.com [192.76.54.20]) by rivendell.linuxpowered.com (Postfix) with ESMTP id 78909980003; Tue, 13 Jul 2004 17:36:49 -0500 (CDT) Message-ID: <40F464DA.4030501@linuxpowered.com> Date: Tue, 13 Jul 2004 17:40:26 -0500 From: Jon Disnard User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Poul-Henning Kamp References: <27296.1089757404@critter.freebsd.dk> In-Reply-To: <27296.1089757404@critter.freebsd.dk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at linuxpowered.com cc: Barney Wolff cc: Drew Broadley cc: current@freebsd.org Subject: Re: CVSUP and 5.2.1 RELEASE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Jul 2004 22:40:38 -0000 Poul-Henning Kamp wrote: >In message <40F45FBC.6010709@corrupt.co.nz>, Drew Broadley writes: > > > >>If you are so much so complaining about the lack of 27 extra characters >>typed by users/admins, >> >> > >That is not the point we (or at least I) are complaining about, the >point is that neither removing the world target nor making it blatter >out a big multicolor linux style README is not a solution. > >The correct solution is the add whatever it takes to make the world >target fail if it is unsafe. > > > Ok that sounds good. I still think a verbose warning at the initiation of "make world" is a good thing though, but possibly only if DESTDIR is not something aside from root. So possibly a system to parse UPDATING, or whatever, for ABI changes and then halting the installworld stages of the world target? 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?