[HEADSUP] Please convert your ports to new options framework

[Chris Rees]

On 9 June 2012 09:38, Thomas Mueller <mueller23 at insightbb.com> wrote:
> from Doug Barton <dougb at FreeBSD.org>:
>
>> > My understanding is that one of the benefits of the new OPTIONS
>
>> On 06/08/2012 06:34, Chris Rees wrote:
>> >> So I have a question from a consumer standpoint as opposed to a
>> >> maintainer standpoint.  If we use portconf to store all of our WITH_*
>> >> options for ports, will that continue to work with ports that have switched
>> >> to optionsng or is there something I need to change in my ports.conf file
>> >> for the options to continue to be recognized?
>
>> With Baptiste's latest work on backwards compatibility this should work
>> fine now, however you should double-check that the same WITH_/WITHOUT_
>> knobs you have in your port.conf are still the ones defined in the
>> ports' Makefiles.
>
>> > I'll make you a nice script for that purpose later.
>
>> Chris, as much as I appreciate your efforts in doing this, asking the
>> user to run scripts to convert stuff is not the answer. We need a ports
>> system that is transparently backwards compatible for users, not one
>> where they constantly have to jump through hoops to make things work
>> again that have worked fine for them for years.
>
>> Doug
>
> Where is all this about the new options framework documented?
>
> There ought to be something in UPDATING file telling users what to do to stay properly in sync.

OPTIONSng is fully backwards compatible-- there have been a few nits
that have been ironed out.  Currently there is no need to do anything
to ensure that everything works fine-- your legacy configuration will
work for the foreseeable future.

Chris