portconf port

Doug Barton dougb at FreeBSD.org
Mon Sep 11 12:57:30 PDT 2006

Doug Hardie wrote:
> I have been trying to figure out how to configure portconf.  The 3
> examples given are not much help with complex ports.  I am starting with
> the dspam port (mail/dspam) as if I can figure that one out the rest
> should be easy. 

That's kind of backwards, but ok. :) The first thing you need to know (and
you're not alone in your confusion on this) is that portconf is not a
replacement for OPTIONS. What portconf allows you to do is store flags on a
per port basis that in the past were usually stored in make.conf, and
therefore were global to all ports. If a port already has OPTIONS, it
doesn't make much sense to try to use portconf (or make.conf) instead. Also,
the OPTIONS framework doesn't modify its behavior based on your flags in
make.conf/ports.conf to start with, so you're better off using it as it was

> I first tried to use the arguments from the configure
> command:

That wouldn't have worked (to prevent downloading spurious dependencies) in
make.conf either, so it won't work here.

> Then I tried to select the options from Makefile entering the options I
> wanted (haven't figured out how to sent the drectories though):

> That skips the options selection menu fine,

The two have nothing to do with each other. You should have seen a message
to the effect of "found a saved configuration for ..." which means that by
default the config target won't bring up the OPTIONS menu again, since there
is already a saved options file for that port. To edit the OPTIONS flags you
need to either do 'make config' or 'make rmconfig ; make'.




    This .signature sanitized for your protection

More information about the freebsd-ports mailing list