On 11/17/13, 6:28 PM, Andrey Repin wrote:
Greetings, David Stacey!
Regarding you second point:
My second point is that I can't tell from looking at a directory, if I'm
inside a working copy or not. Launching any additional tools to do simple
telling is not an option.
This is a major drawback f
ou could have a system where the versioned svn packages
provide only a statically linked binaries and none of the other
libraries, while the unversioned Subversion packages provide
dynamically linked binaries and all the libraries.
*Iff* supporting multiple versions is deemed necessary, this would
On Mon, Nov 18, 2013 at 10:35:58AM -0800, David Rothenberger wrote:
>I know of no other Linux distribution that supports multiple
>installed versions of Subversion. I don't think it's a good idea.
And, as I said, neither do I.
I'm vetoing this idea. I don't think it's something that we want for
On 18/11/13 18:18, Kevin Connor Arpe wrote:
Thanks for your response. I have one more important point to add. I
feel most hard-core UNIX hackers will laugh when I explain. I use
IntelliJ at work which is a Java IDE. It depends upon SVNKit for its
Subversion functionality. SVNKit is a Pure Ja
ess the API bindings which require DLLs to function,
for example the Perl binding used by git-svn. There is also the
Apache module to consider.
I suppose you could have a system where the versioned svn packages
provide only a statically linked binaries and none of the other
libraries, while the unversion
r of other people with the same issue. No on had a simple
solution, but many were wishing for more precise version control in
Subversion-space.
Yes, I an interested to take ownership of the official Subversion
packages for Cygwin.
I was thinking about this type of SVN package setup:
* 1.6.x (svn_1.
On Sun, Nov 17, 2013 at 10:48:23PM +0400, Andrey Repin wrote:
>Greetings, Kevin Connor Arpe!
>>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
Greetings, David Stacey!
> Regarding you second point:
My second point is that I can't tell from looking at a directory, if I'm
inside a working copy or not. Launching any additional tools to do simple
telling is not an option.
This is a major drawback for me, and I'm not upgrading.
> The svn-1.
On 17/11/13 21:11, Andrey Repin wrote:
Normally, you can expect Subversion to transparently operate across different
mix of client and server versions, but they've made a... change[1]... back in
the days, that made working directories illegible in newer (1.7+) clients.
The 1.7 client has the mean
Greetings, Christopher Faylor!
>>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.
On Sun, Nov 17, 2013 at 10:17:39AM -0800, David Rothenberger wrote:
>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
Greetings, Kevin Connor Arpe!
> 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,
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
Il 11/17/2013 11:30 AM, Kevin Connor Arpe ha scritto:
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
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
15 matches
Mail list logo
