From owner-freebsd-arch Wed Aug 29 7:36:59 2001 Delivered-To: freebsd-arch@freebsd.org Received: from ipcard.iptcom.net (ipcard.iptcom.net [212.9.224.5]) by hub.freebsd.org (Postfix) with ESMTP id EC2D737B40B; Wed, 29 Aug 2001 07:36:40 -0700 (PDT) (envelope-from sobomax@FreeBSD.org) Received: from vega.vega.com (dialup9-6.iptelecom.net.ua [212.9.228.6]) by ipcard.iptcom.net (8.9.3/8.9.3) with ESMTP id RAA77260; Wed, 29 Aug 2001 17:36:32 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Received: from FreeBSD.org (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.11.4/8.11.3) with ESMTP id f7TEZLo61158; Wed, 29 Aug 2001 17:35:21 +0300 (EEST) (envelope-from sobomax@FreeBSD.org) Message-ID: <3B8CFDF0.E716421F@FreeBSD.org> Date: Wed, 29 Aug 2001 17:36:32 +0300 From: Maxim Sobolev Organization: Vega International Capital X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en,uk,ru MIME-Version: 1.0 To: Peter Pentchev Cc: Alexander Langer , arch@FreeBSD.org, ports@FreeBSD.org Subject: Re: ports.conf References: <20010828221018.A31427@zerogravity.kawo2.rwth-aachen.d> <3B8CDC38.EC1EE32C@FreeBSD.org> <20010829165544.C780@ringworld.oblivion.bg> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit 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 Peter Pentchev wrote: > 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. Err, as I already clarified I meant *defaults* could be placed into bsd.ports.mk. The whole my point is that I do not see any reason for a separate ${PORTSDIR}/ports.conf (or ports.conf in any other dir in ${PORTSDIR}), which gets unconditionally included into bsd.port.mk. For the record, I do not see any reason for separating user-configurable /etc/ports.conf from /etc/make.conf too, but I do not care either, because I could simply ignore it and continue using /etc/make.conf just like I was doing during the last several years. IMO, proposed change and whole thread in spite of 4.4 release helps nothing and only drives developers' attention from the real problems ("how many bento errors have you fixed today?"). Am I alone feeling like this? -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message