Date: Tue, 10 Dec 2013 19:37:52 -0500 From: drosih@rpi.edu To: mandree@FreeBSD.org Cc: svn-ports-head@freebsd.org, ohauer@FreeBSD.org, svn-ports-all@freebsd.org, ports-committers@freebsd.org Subject: Re: svn commit: r332017 - head/devel/subversion17 Message-ID: <201312110037.rBB0bKED017065@smtp9.server.rpi.edu>
next in thread | raw e-mail | index | archive | help
On Mon, 09 Dec 2013 3:51:14 EST Matthias Andree wrote: > > Am 08.12.2013 23:26, schrieb olli hauer: > > On 2013-12-08 16:09, Matthias Andree wrote: > >> Is there any purpose in keeping old garbage around? > >> Such as new client not working with old server? > >> If not, let's just axe the older versions rather than fix > >> package name conflicts. > >> > > > > > > The subversion java port is fixed, I'm more concerned with ports using > > [lot of details snipped] > > That does not answer the crucial question: > > *What purpose does it serve to keep old subversion ports in the tree?* FWIW, I've had occasions where upgrading subversion to benefit my work on one repository then caused me headaches in some other repositories. I forget the details, but I do know that for a few months I had one freebsd machine where I did not upgrade subversion, because there were repositories (or working copies checked out) which I did not want to upgrade to the most-recent version of that time. I wouldn't put a lot of effort into supporting multiple releases of subversion, but there sometimes is a benefit in being able to build an older release. -- Garance Alistair Drosehn .aka. gad@FreeBSD.org Senior Systems Programmer Rensselaer Polytechnic Institute; Troy NY
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201312110037.rBB0bKED017065>