ports.conf: Is there a reason behind not being default?

Sean C. Farley scf at FreeBSD.org
Tue Dec 18 08:16:23 PST 2007


On Tue, 18 Dec 2007, 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

I find it simpler to use:
editors/vim: WITH_GTK2

or for all vim ports:
editors/vim*: WITH_GTK2

Multiple ports on one line:
multimedia/mencoder multimedia/mplayer: WITH_NVIDIA

Defaults for all ports
*: BATCH                                |\
    SRC_BASE=/usr/FreeBSD/RELENG_7/src   |\
    SYSDIR=/usr/FreeBSD/RELENG_7/src/sys |\
    WITH_NVIDIA_GL

Sean
-- 
scf at FreeBSD.org


More information about the freebsd-ports mailing list