From: Kevin Connor Arpe <kevinarpe@gmail.com>
To: cygwin@cygwin.com
Subject: Fwd: Subversion packages
Date: Sun, 17 Nov 2013 10:31:00 -0000 [thread overview]
Message-ID: <CAFMYRRPZWqSJWZVVGDQLLZ55ZOcD_H9q7UgPr4iZyKw9vr2TbQ@mail.gmail.com> (raw)
In-Reply-To: <CAFMYRRMFGxJhMKNKVgUEs45Lb5dLCf-5vq+Rp5s0H=Eg1yB5kw@mail.gmail.com>
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.
Please share you thoughts on this matter.
Kind regards,
Kevin Connor ARPE
Hongkong
--
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
next parent reply other threads:[~2013-11-17 10:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFMYRRMFGxJhMKNKVgUEs45Lb5dLCf-5vq+Rp5s0H=Eg1yB5kw@mail.gmail.com>
2013-11-17 10:31 ` Kevin Connor Arpe [this message]
2013-11-17 11:12 ` marco atzeri
2013-11-17 18:17 ` David Rothenberger
2013-11-17 19:50 ` Christopher Faylor
2013-11-17 21:20 ` : " Andrey Repin
2013-11-17 23:08 ` David Stacey
2013-11-17 23:35 ` Andrey Repin
2013-11-20 0:55 ` Conrad Halling
2013-11-18 18:18 ` Fwd: " Kevin Connor Arpe
2013-11-18 18:40 ` David Rothenberger
2013-11-18 20:24 ` Christopher Faylor
2013-11-18 20:33 ` Yaakov (Cygwin/X)
2013-11-18 19:12 ` David Stacey
2013-11-17 18:50 ` : " Andrey Repin
2013-11-18 0:42 ` Christopher Faylor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFMYRRPZWqSJWZVVGDQLLZ55ZOcD_H9q7UgPr4iZyKw9vr2TbQ@mail.gmail.com \
--to=kevinarpe@gmail.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).