From owner-freebsd-arch Wed Aug 29 6:56:20 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ringworld.nanolink.com (discworld.nanolink.com [217.75.135.248]) by hub.freebsd.org (Postfix) with SMTP id 40B4A37B408 for ; Wed, 29 Aug 2001 06:56:02 -0700 (PDT) (envelope-from roam@ringlet.net) Received: (qmail 2582 invoked by uid 1000); 29 Aug 2001 13:55:44 -0000 Date: Wed, 29 Aug 2001 16:55:44 +0300 From: Peter Pentchev To: Maxim Sobolev Cc: Alexander Langer , arch@FreeBSD.org, ports@FreeBSD.org Subject: Re: ports.conf Message-ID: <20010829165544.C780@ringworld.oblivion.bg> Mail-Followup-To: Maxim Sobolev , Alexander Langer , arch@FreeBSD.org, ports@FreeBSD.org References: <20010828221018.A31427@zerogravity.kawo2.rwth-aachen.d> <3B8CDC38.EC1EE32C@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3B8CDC38.EC1EE32C@FreeBSD.org>; from sobomax@FreeBSD.org on Wed, Aug 29, 2001 at 03:12:40PM +0300 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Aug 29, 2001 at 03:12:40PM +0300, Maxim Sobolev wrote: > Alexander Langer wrote: > > > Hi folks! > > > > You probably followed the arch-mailinglist. > > > > I want to move all ports-related bits into a ports-specific ports.conf. > > > > Now I need your help: > > - Location of ports.conf? > > $PORTSDIR/ports.conf ? > > $PORTSDIR/defaults/ports.conf ? (my favourite) > > $PORTSDIR/Mk/ports.conf ? > > > > I've also created this patch. > > Ok, now I've read the thread and can give my comments on the topic. To me > it seems that ports.conf file isn't really necessary, because it would be > just another file that gets unconditionally included from the bsd.ports.mk, > perhaps we could just merge content of hypotetic ports.conf with > bsd.ports.mk instead. This would solve "where to put it" and "at which > point to include it" problems. Comments? Errr.. I believe that the whole point of ports.conf is that it is a place for user-specified settings. bsd.port.mk gets unconditionally overwritten at each CVSup run (and not everyone is using checked-out CVS trees); ports.conf does not. The situation is similar to /etc/defaults/rc.conf and /etc/rc.conf. G'luck, Peter -- If the meanings of 'true' and 'false' were switched, then this sentence wouldn't be false. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message