On 17/06/2014 12:35 AM, Michelle Sullivan wrote:
> Lev Serebryakov wrote:
>> Hello, Michelle.
>> You wrote 16 июня 2014 г., 17:40:54:
>>
>>
>>>> I want some "dependant" ports to pick-up options set in "main" port, but
>>>> never ever show "config" dialog/UI. I've tried to set
>>>> OPTIONS_NAME=cat_port, and it set OPTIONS_FILE_SET and OPTIONS_FILE_UNSET
>>>> variables, but not PORT_OPTIONS variable, as this exact ("dependant") port
>>>> doesn't have OPTIONS_DEFINE (of course).
>>>>
>>>> What is proper way to use options in this situation? OPTIONS_SLAVE
>>>> doesn't
>>>> look right, as it override options file. I need something like
>>>> OPTIONS_SLAVE_DEFAULT, which will work as OPTIONS_SLAVE if here is no
>>>> ${OPTIONS_FILE} and could be overridden by ${OPTIONS_FILE}, if it is
>>>> present.
>>>>
>>>>
>>>>
>> MS> Have a look at editors/pico-alpine and mail/alpine that does exactly
>> MS> what you're asking I think.
>> Nope. "make config" in "editoris/pico-alpine" shows dialog. I don't want
>> it at all.
>>
>>
>>
> Yes but that option set is different from that in alpine ... OPTIONS=
> will clear any options (or just remove the options in that port)
>
> Michelle
>
>
make -DBATCH will eliminate the need for dialogue. Though you will need
to set your options, we use /usr/ports/devel/pkgconf extensively to set
configuration options.
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
