Date: Sat, 9 Jun 2012 10:03:44 +0100 From: Chris Rees <crees@FreeBSD.org> To: Thomas Mueller <mueller23@insightbb.com> Cc: Doug Barton <dougb@freebsd.org>, freebsd-ports@freebsd.org Subject: Re: [HEADSUP] Please convert your ports to new options framework Message-ID: <CADLo83-ovNtQMawzmuzJMLvA1=nRXM=Kii0XK_BTSQmA4m00oQ@mail.gmail.com> In-Reply-To: <89.83.12283.17B03DF4@smtp02.insight.synacor.com> References: <89.83.12283.17B03DF4@smtp02.insight.synacor.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9 June 2012 09:38, Thomas Mueller <mueller23@insightbb.com> wrote: > 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. =A0If we use portconf to store all of our WITH= _* >> >> options for ports, will that continue to work with ports that have sw= itched >> >> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83-ovNtQMawzmuzJMLvA1=nRXM=Kii0XK_BTSQmA4m00oQ>