Date: Fri, 11 Jan 2013 18:29:31 +0100 (CET) From: Gerald Pfeifer <gerald@pfeifer.com> To: ports-committers@freebsd.org Cc: svn-ports-head@freebsd.org, svn-ports-all@freebsd.org Subject: Re: svn commit: r310063 - in head: . sysutils/cfengine Message-ID: <alpine.LNX.2.00.1301101608200.15650@tuna.site> In-Reply-To: <20130108071049.GP85686@ithaqua.etoilebsd.net> References: <201301080433.r084X9IR015052@svn.freebsd.org> <20130108071049.GP85686@ithaqua.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 8 Jan 2013, Baptiste Daroussin wrote: >> With this change, users can install the sysutils/cfengine >> port, and by default track the latest major version of the >> software. Subsequent version releases, for example the 3.5 >> branch, will not require any interaction from user side. > Nice! In my opinion this should be followed by all/most? ports > with multi version in the ports tree, this will fix also fix > tracking in binary work major upgrades (aka change of default > version) with no manuall intervention. I'd soften this statement a bit: It looks like a good idea to have a canonical version in those cases where we have several in the tree. That should not necessarily be the latest major (or "major") version, though. For example, with lang/gcc I am planning to switch to a newer codebase with the upstream .2 release or so, perhaps .1, perhaps .3, but not .0 in general (for several reasons, also including _other_ ports not being ready yet and needing some ripening upstream). Gerald
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.LNX.2.00.1301101608200.15650>