From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.com
Subject: Re: introduction, fix for npm w.r.t. git, and questions
Date: Wed, 20 Apr 2016 19:30:00 -0000 [thread overview]
Message-ID: <20160420185011.GJ2345@dinwoodie.org> (raw)
In-Reply-To: <BLUPR03MB230DECD3A735AF3CB2225CBDF6D0@BLUPR03MB230.namprd03.prod.outlook.com>
On Wed, Apr 20, 2016 at 03:21:27PM +0000, Brian Clifton wrote:
> (I've never joined a mailing list so please bear with me as I learn how this works)
Hi Brian, welcome!
> I saw the email chain regarding Git using Windows paths; I wanted to
> share that I've been fighting that too. Specifically, npm will fail
> npm installs because it will try to use the Windows path. I submitted
> the following PR to fix that:
>
> https://github.com/npm/npm/pull/12366
My JavaScript is somewhat rusty, and I've never used npm, but it looks
to me that the problem here is that npm's `process.platform` in `git.js`
is set to 'win32'. Cygwin isn't 'win32' -- it's a fundamentally
different beast that just happens to sit on top of Windows -- so
attempting to treat Cygwin as Windows is going to cause all sorts of
pain.
I think the "correct" fix would be to get npm (or possibly the
JavaScript engine itself?) to stop acting as if it's in a Windows
environment when it's running under Cygwin; the Cygwin environment is
much more like a *nix environment than anything else. I've no idea what
that change would involve, though.
> With how many folks experience issues w/ git on Cygwin,
> I'd like to help popularize *some* kind of fix, whatever it might be,
> since NPM and likely other projects are not willing to support Cygwin.
This sort of experience is, as best I can tell, pretty rare actually.
Generally if you have a user (or a process) running within Cygwin, it's
expecting to use POSIX-style paths exclusively -- the whole point of
Cygwin being to provide a POSIX-like environment on Windows -- and the
only time you need to think about Windows-style paths is if you're
calling a native Windows application from within Cygwin (at which point
you normally know that's what you're doing and can use cygpath).
--
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:[~2016-04-20 18:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 15:31 Brian Clifton
2016-04-20 15:44 ` Eliot Moss
2016-04-20 19:30 ` Adam Dinwoodie [this message]
2016-04-20 20:37 ` silverwind
2016-04-20 21:05 ` Adam Dinwoodie
2016-04-20 22:10 ` silverwind
2016-04-20 23:14 ` Adam Dinwoodie
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=20160420185011.GJ2345@dinwoodie.org \
--to=adam@dinwoodie.org \
--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).