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 different things that could make a difference to an executable's behaviour)?
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, not with awk, sed, or whatever. And I'd like to fix that specific problem, not eliminate hunger in the world, or do whatever more general. To achieve that, I've pointed out a non-intrusive and harmless change in CygWin SVN, which might help to resolve that problem.
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 path), but what's got that to do with svn? The fact that it resides in the CygWin bin directory doesn't mean it is also a CygWin binary. Jochen SAG Consulting Services GmbH - Sitz/Registered office: Uhlandstraße 9, 64297 Darmstadt, Germany - Registergericht/Commercial register: Darmstadt HRB 85598 Geschäftsführer/Managing Directors: Klaus Katz, Arno Theiß - http://www.softwareag.com/ -- 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
