From owner-freebsd-ports@FreeBSD.ORG Wed Dec 19 17:29:55 2007 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF3C416A417 for ; Wed, 19 Dec 2007 17:29:55 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by mx1.freebsd.org (Postfix) with SMTP id 38C9F13C447 for ; Wed, 19 Dec 2007 17:29:54 +0000 (UTC) (envelope-from LoN_Kamikaze@gmx.de) Received: (qmail invoked by alias); 19 Dec 2007 17:29:53 -0000 Received: from nat-wh-1.rz.uni-karlsruhe.de (EHLO homeKamikaze.norad) [129.13.72.169] by mail.gmx.net (mp030) with SMTP; 19 Dec 2007 18:29:53 +0100 X-Authenticated: #5465401 X-Provags-ID: V01U2FsdGVkX19C+Kc+5MhCiMLLBN2HG1EFKkCg3EVMEoR8brcHqE ykyKQZX75qfvON Message-ID: <4769550A.4090007@gmx.de> Date: Wed, 19 Dec 2007 18:29:46 +0100 From: Dominic Fandrey User-Agent: Thunderbird 2.0.0.9 (X11/20071203) MIME-Version: 1.0 To: Rong-en Fan References: <4767283D.70604@delphij.net> <20071218144900.M51742@FreeBSD.org> <4767F263.2000708@gmx.de> <6eb82e0712190244p51042783vf8fd1d52a297c90d@mail.gmail.com> In-Reply-To: <6eb82e0712190244p51042783vf8fd1d52a297c90d@mail.gmail.com> X-Enigmail-Version: 0.95.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: ports@freebsd.org, Pav Lucistnik , d@delphij.net Subject: Re: ports.conf: Is there a reason behind not being default? 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: Wed, 19 Dec 2007 17:29:56 -0000 Rong-en Fan wrote: > On Dec 19, 2007 12:16 AM, Dominic Fandrey wrote: >> Pav Lucistnik wrote: >>> On Mon, 17 Dec 2007 17:54:05 -0800, Xin LI wrote >>> >>>> I think that ports-mgmt/portconf (a.k.a. /usr/local/etc/ports.conf) >>>> is a very handy feature that makes it much easier to store port options >>>> across upgrade. Is there a reason behind not making it into >>>> bsd.ports.mk? IMHO it's a big deal to take the script into >>>> ports/Tools/scripts, and move the configuration to somewhere like >>>> /etc/ports.conf... >>> I haven't checked it out yet. What can it do that can't be done in >>> /etc/make.conf with constructs like >>> >>> .if ${.CURDIR} == "/usr/ports/editors/vim" >>> WITH_GTK2=yes >>> .endif >>> >>> ? >> Actually it can only do less than that (and it won't work if /usr/ports is a >> symlink, at least the last time I checked). The only advantage is a more > > It can, see commit log > > http://www.freebsd.org/cgi/cvsweb.cgi/ports/ports-mgmt/portconf/pkg-install Why doesn't it do something like PORTSDIR!=cd /usr/ports && pwd -P || exit 0 to avoid having to hard-code it during install?