Bug 24018 which appears to be a showstopper for running Cygwin on Wine

[Peter Rosin]

On 2013-06-28 23:37, Hin-Tak Leung wrote:
> --- On Fri, 28/6/13, Alan W. Irwin <irwin at beluga.phys.uvic.ca> wrote:
> 
> ... However, because of the Cygwin fork
>> bug, Cygwin on
>> Wine has largely been untested for the last three years so
>> this could
>> be a good opportunity to do such testing for the combination
>> of Cygwin
>> (with the fork fix) and recent Wine in case some Wine
>> regression is
>> discovered by such testing.
> 
> what????!!!! You really don't get it. setup.exe is simply *not* a necessity for putting a cygwin installation under wine. There are many other ways of installing cygwin into wine without running cygwin's installer. The easiest is simply to copy the entire installed directory, plus importing a few registry entries, from a genuine windows box which has cygwin on.
> 
> (There are many people who bundles bits of cygwin with their software for windows, for years; so if you are a full-time windows user, you might even gain some bits of cygwin without knowing it, and without ever having seen the official cygwin installer or even heard of it) . The problem is that even if you manage to put it on, many part of cygwin don't work correctly under wine.
> 
> Please don't confuse issues with running the official installer, and issues with running the cygwin system (or part of) itself. You have been told *many times*, in that thread, that setup.exe itself does not depend on cygwin, and use no part of it.

Running the official installer invokes child processes that do indeed
require a functioning Cygwin DLL. I.e. post-install scripts (and pre-
remove scripts, but we're talking about the initial install so that's
out of scope).

The registry entries you speak about are a thing of the past, if you
are referring to mount points.

Cheers,
Peter