From owner-freebsd-ports@FreeBSD.ORG Sat Jan 7 07:56:36 2006 Return-Path: X-Original-To: ports@freebsd.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0188F16A41F for ; Sat, 7 Jan 2006 07:56:36 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.12]) by mx1.FreeBSD.org (Postfix) with SMTP id 1BABE43D48 for ; Sat, 7 Jan 2006 07:56:34 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 31190 invoked by uid 399); 7 Jan 2006 07:56:34 -0000 Received: from localhost (HELO ?192.168.1.100?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 7 Jan 2006 07:56:34 -0000 Message-ID: <43BF7430.80509@FreeBSD.org> Date: Fri, 06 Jan 2006 23:56:32 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (X11/20051226) MIME-Version: 1.0 To: Tobias Roth References: <834B3A07-EC76-4645-8E1B-7ABEA4EC999A@submonkey.net> <43BE57E9.9060507@rogers.com> <43BE61C9.9060502@ebs.gr> <43BE63E7.4060209@rogers.com> <20060106124508.GB14967@droopy.unibe.ch> <20060106125428.GC79296@pcwin002.win.tue.nl> <20060106131231.GC14967@droopy.unibe.ch> In-Reply-To: <20060106131231.GC14967@droopy.unibe.ch> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org Subject: New rc.d code merge timing (Was: Re: Portupgrade confused about editors/emacs) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Jan 2006 07:56:36 -0000 Tobias Roth wrote: > This (at least from my part) was not critique on the responsivenes, > but on the time and nature of the MFC. I claim it was not long enough in > CURRENT to be MFCed. And since it was known beforehand that the change > will possibly affect many port maintainers who will then have to adapt > their ports, the time of the MFC was was badly chosen. If I commit or > MFC something that I can fix myself during holiday season, that's ok. > But if I commit something that needs the help of many people, in case it > breaks, the holiday season is a bad moment to commit. Tobias, Your point here has a lot of merit, and I think it's worth my explaining the reasoning for doing this the way I did. The primary motivating factor was the upcoming freeze for the RELENG_6 branch on January 30. We knew that the code in the base was sound, and did what it was supposed to do. We also knew that there were going to be some ports that needed fixing. The problem is that we have a chicken and egg issue here. A lot of testing was done on the boot scripts of a lot of ports, but not only were errors discovered in boot scripts that seemed perfectly valid, but many of the problems we're seeing now are related to ordering issues. This in turn depends on what combination of ports that the user has installed. All the testing in the world would not have uncovered every possible way for this to break, although it might have reduced some of the pain. Ultimately, this is going to be part of the process of enabling this functionality any way you slice it. It's also worth noting, although I've posted these stats before, that there are roughly 650 ports that install boot scripts. Of these, 350 have been converted to new style rc.d, the others have not. The 300 that have not been converted are not affected by this change. Of the 350 that have been converted, very few have exhibited problems. That's not to say that the problems we've seen aren't important, and obviously they need to be fixed. However this is a pretty good track record overall. At the end of the day, and after extensive discussion with the various stakeholders, I made the decision to MFC sooner than later in order to get things as cleaned up as possible before the freeze. I still think that's the right decision, but I acknowledge that reasonable minds could differ on this topic. Regards, Doug -- This .signature sanitized for your protection