From: Jochen Wiedmann <jochen.wiedmann@softwareag.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: CygWin SVN should identify as CygWin
Date: Tue, 07 Aug 2012 14:20:00 -0000 [thread overview]
Message-ID: <5021233D.1010305@softwareag.com> (raw)
In-Reply-To: <CE9C056E12502146A72FD81290379E9A43657CCF@ENFIRHMBX1.datcon.co.uk>
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
next prev parent reply other threads:[~2012-08-07 14:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5020CEC7.3010703@softwareag.com>
2012-08-07 9:47 ` marco atzeri
2012-08-07 10:07 ` Jochen Wiedmann
2012-08-07 10:37 ` Andrey Repin
2012-08-07 10:41 ` Jochen Wiedmann
2012-08-07 11:25 ` Adam Dinwoodie
2012-08-07 14:20 ` Jochen Wiedmann [this message]
2012-08-07 15:08 ` Adam Dinwoodie
2012-08-07 15:25 ` Larry Hall (Cygwin)
2012-08-07 17:15 ` Andrey Repin
2012-08-08 16:30 ` Jochen Wiedmann
2012-08-07 14:35 ` Andrey Repin
2012-08-08 16:58 ` David Rothenberger
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=5021233D.1010305@softwareag.com \
--to=jochen.wiedmann@softwareag.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).