On 8 June 2012 23:01, Doug Barton <do...@freebsd.org> wrote:
> 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.
>

Oh no, you're absolutely right, however people do need to migrate
their configurations so we're not supporting this in ten years from
now.  The compat code needs ripping out at some point, and the more
time people have to migrate (and test!) the better.

Chris
_______________________________________________
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"

Reply via email to