From owner-freebsd-arch@FreeBSD.ORG Tue Feb 24 07:25:26 2004 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E132716A4CE for ; Tue, 24 Feb 2004 07:25:25 -0800 (PST) Received: from srv01.sparkit.no (srv01.sparkit.no [193.69.116.226]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B34A43D1F for ; Tue, 24 Feb 2004 07:25:25 -0800 (PST) (envelope-from eivind@FreeBSD.org) Received: from ws ([193.69.114.88]) by srv01.sparkit.no (8.12.10/8.12.10) with ESMTP id i1OFPEJO097122; Tue, 24 Feb 2004 16:25:14 +0100 (CET) (envelope-from eivind@FreeBSD.org) Received: from ws (localhost [127.0.0.1]) by ws (8.12.9/8.12.10) with ESMTP id i1OFOImd004098; Tue, 24 Feb 2004 15:24:18 GMT (envelope-from eivind@ws) Received: (from eivind@localhost) by ws (8.12.9/8.12.10/Submit) id i1OFOHdq004097; Tue, 24 Feb 2004 15:24:17 GMT (envelope-from eivind) Date: Tue, 24 Feb 2004 15:23:16 +0000 From: Eivind Eklund To: Oliver Eikemeier Message-ID: <20040224152316.GB3364@FreeBSD.org> References: <20040223084146.GA4202@mobile.acs-et.com> <4039D9FF.40208@fillmore-labs.com> <20040224072401.GB1125@mobile.acs-et.com> <403B206B.7000101@fillmore-labs.com> <20040224103932.GA20467@mobile.acs-et.com> <403B403C.7040701@fillmore-labs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <403B403C.7040701@fillmore-labs.com> User-Agent: Mutt/1.5.4i cc: freebsd-arch@FreeBSD.org Subject: Re: rc.d and ports X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2004 15:25:26 -0000 On Tue, Feb 24, 2004 at 01:14:52PM +0100, Oliver Eikemeier wrote: > Mike Makonnen wrote: > >>them > >>to go away with the port. Nobody (and especially not ports) should edit > >>whatever/defaults/rc.conf, and how would I otherwise cope with the > >>situation > >>that default flags may change? > > > >Then the ports can use /usr/local/etc/rc.conf.d. When the port is deleted > >it can just delete the appropriate conf file in that directory without the > >need to edit any files. > > ${PREFIX}/etc/rc.conf.d files may be edited by the user, so you can't simply > delete them. Yes, we can. These are defaults *as supplied from FreeBSD*, and editing them is an error. I think that we might want a more telling name (${PREFIX}/etc/defaults/rc.conf.d/ or ${PREFIX}/etc/rc.conf.defaults/ - I prefer the former). If we want to be really friendly, we might also want to allow per-port override files, make sure the defaults are suitably labelled inside each file, and set them schg so the user have to work really hard to shoot himself in the foot. But if we use default files, we definately can and should delete them when we wipe the port. The other alternative is to use a full merge system for port config files. I've put up a draft of a design for extending etcmerge to support this at http://people.freebsd.org/~eivind/etcmerge.ports However, having parts of the system come and go at will is a really hard job for any config file manager. Eivind.