From owner-freebsd-arch Wed Aug 29 14:28:49 2001 Delivered-To: freebsd-arch@freebsd.org Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11]) by hub.freebsd.org (Postfix) with ESMTP id E54C937B405; Wed, 29 Aug 2001 14:28:37 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@[147.11.46.201]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id OAA10450; Wed, 29 Aug 2001 14:28:36 -0700 (PDT) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3B8CDC38.EC1EE32C@FreeBSD.org> Date: Wed, 29 Aug 2001 14:28:41 -0700 (PDT) From: John Baldwin To: Maxim Sobolev Subject: Re: ports.conf Cc: ports@FreeBSD.org, arch@FreeBSD.org, Alexander Langer 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 29-Aug-01 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? ports.conf is useful for the same reason that we have make.conf instead of making people read bsd.foo.mk buried in some obscure directory: it's more convenient to users. Also, ports/Mk/ports.conf can easily just be a default file with everything commented out that doesn't even get included. Rather, if a user wants to customize, they create a /etc/ports.conf with teh appropriate knobs set, and bsd.port.mk just includes /etc/ports.conf. The reason for putting the default ports.conf in ports/Mk (or ports/defaults?) instead of /usr/share/examples or some such is the same reason the ports makefiles are in ports/Mk and not /usr/share/mk: it needs to be in sync with the ports tree. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message