Date: Tue, 10 Dec 2013 11:55:40 +0100 From: olli hauer <ohauer@gmx.de> To: Matthias Andree <mandree@FreeBSD.org> Cc: svn-ports-head@freebsd.org, Olli Hauer <ohauer@FreeBSD.org>, svn-ports-all@freebsd.org, ports-committers@freebsd.org, Mathieu Arnold <mat@FreeBSD.org>, Tijl Coosemans <tijl@FreeBSD.org> Subject: Re: svn commit: r332017 - head/devel/subversion17 Message-ID: <52A6F32C.7000706@gmx.de> In-Reply-To: <52A58482.2070708@FreeBSD.org> References: <201310292201.r9TM15df056478@svn.freebsd.org> <EE1C4CE479CEC1E30C7895E9@ogg.in.absolight.net> <20131207150704.5ff18aae@kalimero.tijl.coosemans.org> <52A48BAF.8050607@FreeBSD.org> <52A4F213.7060303@gmx.de> <52A58482.2070708@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2013-12-09 09:51, 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?* > In an ideal world (dream) you have only FreeBSD systems, where the OS and ports like subversion and others are prod. ready even in 0/1 releases. However for many of us this ideal world does not exist. E.g have software in production that is using svnkit (even more worse an older version of svnkit) that is not compatible with 1.7/1.8 SVN backends (was there, had to rollback some systems).
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52A6F32C.7000706>