public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Koontz <brianko@gmail.com>
To: Adam Dinwoodie <adam@dinwoodie.org>
Cc: cygwin@cygwin.com, ASSI <Stromeko@nexgo.de>
Subject: Re: 3.3.0: Possible regression in cygwin DLL (Win10); fixed in snapshot
Date: Mon, 8 Nov 2021 17:18:04 -0600	[thread overview]
Message-ID: <7601C26F-3ECC-4DC4-930E-D8A7BE3FC10D@gmail.com> (raw)
In-Reply-To: <CA+kUOanm+sQsY2HJcxJmaGpjcPoTes55QL34iru5Hnz0LPNchg@mail.gmail.com>

Unfortunately, users don’t always have the time or chops to write wrappers for missing Cygwin packages or functionality. By its very nature, a Cygwin environment will always involve non-Cygwin components . In this case, the GCM-Core devs are actively working on a Cygwin solution and were able to pinpoint the cause.

I’m a developer too, just not a Cygwin dev. I know what it’s like being forced to work in a mixed environment. Whenever possible, I prefer Cygwin packages if they are available. Even then, the environment will always remain mixed. I wouldn’t report a bug I suspected was caused by the mixed environment. This wasn’t one of those situations.

Thanks for all the work you all do with Cygwin. My work would be exponentially more inefficient without Cygwin.

Brian

> On Nov 8, 2021, at 2:50 PM, Adam Dinwoodie <adam@dinwoodie.org> wrote:
> 
> 
> 
> Cygwin Git is not inherently an appropriate wrapper to allow Cygwin
> applications to seamlessly communicate with non-Cygwin Windows
> applications. Naively mixing the two will work sometimes, but it's
> reasonable to expect problems due to, for example, the fact that a
> native Windows application and a Cygwin application will have very
> different ideas about the absolute path to a given file.
> 
> In this case, it looks like the change of behaviour was an unintended
> side-effect of changes made to the Cygwin DLL, and the folk working on
> the DLL have found a way to get things working as expected for Brian.
> Nonetheless I agree with Achim, and in general I wouldn't expect the
> steps Brian was taking to work reliably anyway. I would expect that,
> to get things working within Cygwin's design paradigms, one would need
> to either (a) compile GCM as a Cygwin application, (b) not use Cygwin
> at all and instead swap to Git for Windows, or (c) write a shim
> application that uses native Windows APIs to talk to GCM and
> *nix-style Cygwin APIs to talk to Cygwin Git.
> 
> -- 
> Problem reports:      https://cygwin.com/problems.html
> FAQ:                  https://cygwin.com/faq/
> Documentation:        https://cygwin.com/docs.html
> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2021-11-08 23:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 15:02 Brian
2021-11-05  3:39 ` Takashi Yano
     [not found]   ` <CAEv6GOA-y58YrftXgEgFrjqtOTHmfdu2Vrq76Lwn0suZpZ=U9w@mail.gmail.com>
2021-11-05  8:05     ` Takashi Yano
2021-11-05 13:42       ` Brian
2021-11-05 19:41         ` Takashi Yano
2021-11-05 20:08           ` Ken Brown
2021-11-06 16:22             ` Ken Brown
2021-11-05 21:32           ` Brian
2021-11-06  6:24         ` ASSI
2021-11-08 16:30           ` Andrey Repin
2021-11-08 20:49             ` Adam Dinwoodie
2021-11-08 23:18               ` Brian Koontz [this message]

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=7601C26F-3ECC-4DC4-930E-D8A7BE3FC10D@gmail.com \
    --to=brianko@gmail.com \
    --cc=Stromeko@nexgo.de \
    --cc=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).