Which ports store/use OPTIONS (/var/db/ports/portname/options)?

Sam Lawrance lawrance at FreeBSD.org
Mon Feb 27 23:33:07 PST 2006


On 28/02/2006, at 5:07 AM, Freddie Cash wrote:

> On Monday 27 February 2006 09:47 am, Scot Hetzel wrote:
>> On 2/27/06, Chris Shenton <chris at shenton.org> wrote:
>>> Some ports store their configuration options into
>>> /var/db/ports/portname/options, one example is gaim.
>
>>> Other ports don't, like www/apache22.  This is annoying because I
>>> have to remember when I rebuild it, and portupgrade won't get my
>>> needed tweaks like WITH_PROXY_MODULES.
>
>>> For apache22 I've set my needed tweaks in /etc/make.conf but that
>>> doesn't seem the best place, especially since the config names  
>>> are so
>>> generic, like WITH_SSL_MODULES.
>
>>> So why do some ports save these and others don't? Am I not doing
>>> something required to get it to save these?
>
>> There are several reasons why some ports save the options and others
>> don't.
>
>> 1. Port Maintainer hasn't had time to update their port to use  
>> OPTIONS.
>
>> 2. Port Maintainer resists the use of OPTIONS because the port will
>> then display a dialog, and then require the user to choose which
>> options to build.
>
>> 3. Users of the FreeBSD Ports collection don't like ports that use
>> OPTIONS, because a dialog box may appear for a dependancy.
>
>>    The reason for this is some of the users start building a port,
>> they then walk away from the system to let the process finish.  But
>> during the build process, a dependancy shows its OPTIONS dialog, this
>> causes the build process to pause until the operator comes back and
>> chooses which options the dependancy will build with.  This repeats
>> for each dependancy that is using OPTIONS.
>
> This can also be solved by using "make config-recursive" to bring  
> up all
> the OPTIONS screens for all the dependencies, before running "make
> install".  That way, you configure all the ports that will be  
> installed
> before the build begins, and you can safely walk away during the  
> build.

Or, unless you know you need something special, run with the defaults  
by using -DBATCH.



More information about the freebsd-ports mailing list