From owner-freebsd-ports@FreeBSD.ORG Thu Jun 9 21:30:23 2005 Return-Path: X-Original-To: freebsd-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 449B516A41C for ; Thu, 9 Jun 2005 21:30:23 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail1.fluidhosting.com (mail1.fluidhosting.com [66.150.201.101]) by mx1.FreeBSD.org (Postfix) with SMTP id E123643D1D for ; Thu, 9 Jun 2005 21:30:22 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 9100 invoked by uid 399); 9 Jun 2005 21:30:14 -0000 Received: from unknown (HELO ?192.0.35.182?) (dougb@dougbarton.net@192.0.35.182) by mail1.fluidhosting.com with SMTP; 9 Jun 2005 21:30:14 -0000 Message-ID: <42A8B4E6.9090401@FreeBSD.org> Date: Thu, 09 Jun 2005 14:30:14 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-ports@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Including PREFIX/etc/rc.d/* scripts in the system's rcorder for startup in 6.0-Release 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: Thu, 09 Jun 2005 21:30:23 -0000 Howdy, I realize that this is pretty short notice before the release, but the rc.d team just got a spiffy new volunteer to do the legwork on this, and so we're going to try to beat the code freeze/slushie deadline for 6.0. What we've been discussing for the last few days on the freebsd-rc list is a two-fold approach in order to avoid needing a flag day to cover this issue. The first part of the approach is to hack /etc/rc.d/localpkg to use rcorder to handle the keywords that are already in the scripts with *.sh filename patterns. This will preserve the lexical ordering that exists now, while giving port authors (and users of course) the ability to start using keywords with existing scripts that fit the *.sh pattern. Part two of this proposal is to hack on /etc/rc to use rcorder on any scripts in PREFIX/etc/rc.d that DON'T use the *.sh filename pattern, but DO include a new keyword (that will be specified). In this way, port authors and users can start opting into the new system at their convenience. Once the new system has been in place "long enough," we can drop processing for the special key word, and just handle all rc.d scripts the same, regardless of their location. This may sound more complicated than it needs to be, but the discussion on the freebsd-rc list brought up a lot of interesting cases that need to be considered as part of this transition, and I believe we've simplified it as much as possible. My question at this point is, does this approach sound reasonable? Our intention is to coordinate this closely with y'all so that we don't do something that will break the new release, or more importantly break backwards computability. Thanks, Doug -- This .signature sanitized for your protection