Date: Sat, 09 Jun 2012 04:38:09 -0400 From: "Thomas Mueller" <mueller23@insightbb.com> To: freebsd-ports@freebsd.org Cc: Doug Barton <dougb@FreeBSD.org> Subject: Re: [HEADSUP] Please convert your ports to new options framework Message-ID: <89.83.12283.17B03DF4@smtp02.insight.synacor.com>
next in thread | raw e-mail | index | archive | help
from Doug Barton <dougb@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. Tom
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?89.83.12283.17B03DF4>