X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding
	:reply-to; q=dns; s=default; b=taLZPErYl7fjpKX6bL6QedxaGpdtTG141
	xoktpoilu7OU3kniSxifRUm4slddlsQP9xOBhu9rqgrAKolaCfl6VA3WmBKyV7m6
	ov/xnQ7TSnR+guVbtUHwtuDWC8kP/CU0aqRKp+d2IIPsBBtafukYjiToMBKVLqAW
	9lJ/9NB59Q=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding
	:reply-to; s=default; bh=kaBDETOP764ozIvRJQTqPcY+qCY=; b=Vq1Fauc
	A2BmNSzhIPL1uDxjdBRgEFm9hsO39ji7oNZRBzadVbE5Yn8vnbBXNYAOszsRTSWI
	9N/a2ubJvsaEOarc+7TNSKJ/3s0wHqVuCkk0xEEQyeXtksvEYbC0CNQxElOL8DV/
	bwGgZAnpvHVhOxGrbcpCGz0dW33y+mJYuSeY=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=1.8 required=5.0 tests=AWL,BAYES_50,RDNS_NONE,SPF_SOFTFAIL,URIBL_BLOCKED autolearn=no version=3.3.2
X-HELO:	qmta14.emeryville.ca.mail.comcast.net
Message-ID:	<52890843.90903@acm.org>
Date:	Sun, 17 Nov 2013 10:17:39 -0800
From:	David Rothenberger <daveroth AT acm DOT org>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Fwd: Subversion packages
References:	<CAFMYRRMFGxJhMKNKVgUEs45Lb5dLCf-5vq+Rp5s0H=Eg1yB5kw AT mail DOT gmail DOT com> <CAFMYRRPZWqSJWZVVGDQLLZ55ZOcD_H9q7UgPr4iZyKw9vr2TbQ AT mail DOT gmail DOT com>
In-Reply-To:	<CAFMYRRPZWqSJWZVVGDQLLZ55ZOcD_H9q7UgPr4iZyKw9vr2TbQ@mail.gmail.com>
X-IsSubscribed:	yes
Reply-To:	cygwin AT cygwin DOT com

On 11/17/2013 2:30 AM, Kevin Connor Arpe wrote:
> Hello,
> 
> Cygwin currently offerers two Subversion packages.  One from 1.7.x
> series and another from 1.8.x series.
> 
> Subversion version series are important because local repositories
> created by each series (1.6.x, 1.7.x, 1.8.x) are incompatible.  In
> short, if you do "svn checkout" with svn 1.6.x, you cannot do "svn
> update" with svn 1.7.x or 1.8.x.  For a variety of reasons, at my
> office, I am forced to use svn 1.6.x series.  This precludes me from
> using standard pre-built Cygwin packages for Subversion work.  I'm
> always jumping back to a IDE or DOS box to manage my svn local repos.
> 
> I'm not here to complain about this "feature" of Subversion.  AFAIK:
> Cygwin seems to normally provide at least two versions of any package.
>  That's great, and usually helps.  However, this situation is a bit
> rare.  I would like to help make each series available in Cygwin.
> I've done some googling on this matter and noticed a few others asking
> on mailing lists (not Cygwin, I think) about how to get svn 1.6.x on
> the latest Cygwin.  Frankly, there were no satisfying answers.
> 
> As a starter, I am happy to volunteer to create a specific Cygwin
> package for Subversion 1.6.x.  Additionally, I already built my own
> copy of Subversion 1.6.x using Cygwin build toolchain.

The problem is that the Cygwin installer does not provide a mechanism
for having more than two versions of the same package. I currently
provide (a somewhat out-of-date) 1.7 version as "prev" and the latest
1.8 as "curr". I can see no way to also provide 1.6.

We could make another package (subversion_1_6 or something), but users
could not have both that and the "subversion" package installed at the
same time. I really don't think that's a great packaging decision.

Upstream makes no provisions for having multiple installed versions
coexist. Packaging subversion for Cygwin already involves quite a few
local patches; I'm not interested in developing and maintaining patches
to allow multiple versions to coexist.

The newer versions are able to communicate with older servers. Why can't
you just upgrade to 1.7 or 1.8 for the client? If there is some real
reason you cannot, I suspect your effort would be better spent trying to
change that reason instead of packaging 1.6. Especially since even
upstream no longer supports 1.6. However, if you really want to make
this work and are willing to take over packaging of all versions of
subversion and its dependencies, I'm happy to relinquish the
maintainership to you. I've almost completely switch to git myself anyway.

-- 
David Rothenberger  ----  daveroth AT acm DOT org

divorce, n:
        A change of wife.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -