On 07.08.2012 18:30, Andrey Repin wrote:
Subversion libraries supposed to be linked directly, not used through svn
command-line wrapper.
For more details, go read http://svn-book.org/
Quite obviously, you never attempted to support a diverse user basis
(just think of all the platforms) in
On 8/7/2012 1:16 AM, Jochen Wiedmann wrote:
from what I can tell, a user of CygWin SVN has no possibilities to be
aware of the fact that it is indeed CygWin SVN, and not another program.
This is the root cause for problems like
http://jira.codehaus.org/browse/SCM-213
As the volunteer
Hi,
I apologize if I didn't pick the proper mailing list, but discussion
about packages sounded right to me...
from what I can tell, a user of CygWin SVN has no possibilities to be
aware of the fact that it is indeed CygWin SVN, and not another program.
This is the root cause for problems
On Tue, Aug 07, 2012 at 10:16:07AM +0200, Jochen Wiedmann wrote:
Hi,
I apologize if I didn't pick the proper mailing list, but discussion
about packages sounded right to me...
cygwin-apps: a subscriber-only list for discussing packaging issues
regarding applications that are distributed
On 8/7/2012 10:16 AM, Jochen Wiedmann wrote:
Hi,
I apologize if I didn't pick the proper mailing list, but discussion
about packages sounded right to me...
wrong mailing list.
Packages is for discussion between package managers,
not for bugs or help.
Forwarded to the right one: cygwin
On 07.08.2012 11:45, marco atzeri wrote:
I do not understand why you need different file for cygwin.
You gave the answer just below, Marco:
Commit on cygwin should follow cygwin rules (unix like),
so something like
SAG Consulting Services GmbH - Sitz/Registered office: Uhlandstraße
Greetings, Jochen Wiedmann!
On 07.08.2012 11:45, marco atzeri wrote:
I do not understand why you need different file for cygwin.
You gave the answer just below, Marco:
Commit on cygwin should follow cygwin rules (unix like),
so something like
I don't get this topic. At all.
And i'm using
On 07.08.2012 12:27, Andrey Repin wrote:
To all extents and purposes, Cygwin SVN behave just the way I'd expect
from it.
I didn't say, it behaves wrong. My point is that I need to know that I
am using it, and not another svn, if all I know is there's a svn binary
in my path.
Jochen
Jochen Wiedmann wrote:
I didn't say, it behaves wrong. My point is that I need to know that I
am using it, and not another svn, if all I know is there's a svn binary
in my path.
This isn't Subversion's responsibility; the problem is more general: how do you
tell if the version of awk, sed or vim
On 07.08.2012 13:15, Adam Dinwoodie wrote:
This isn't Subversion's responsibility; the problem is more general: how do you
tell if the version of awk, sed or vim are Cygwin ones or not (or ones compiled
containing a specific patch, or built on a particular day, or any other of a
myriad of
Greetings, Jochen Wiedmann!
To all extents and purposes, Cygwin SVN behave just the way I'd expect
from it.
I didn't say, it behaves wrong. My point is that I need to know that I
am using it, and not another svn, if all I know is there's a svn binary
in my path.
For what reason?
Also,
Jochen Wiedmann wrote:
On 07.08.2012 13:15, Adam Dinwoodie wrote:
This isn't Subversion's responsibility; the problem is more general: how do
you
tell if the version of awk, sed or vim are Cygwin ones or not (or ones
compiled
containing a specific patch, or built on a particular day, or any
On 8/7/2012 10:16 AM, Jochen Wiedmann wrote:
And, besides, your proposed solution won't work: I could, of course,
use which, or where to deduce the location of svn, but what would
that tell me. Assuming, I get /usr/bin/svn, then I'd know that which
is a CygWin binary (because it emits a CygWin
Greetings, Jochen Wiedmann!
I don't know about more general. However, I know very well that
there's a particular project (Maven Release Plugin), which has this very
problem with svn,
Then this is problem of Maven.
Subversion libraries supposed to be linked directly, not used through svn
14 matches
Mail list logo
