From: noer AT cygnus DOT com (Geoffrey Noer)
Subject: Re: builtin shell commands in a Makefile --  cygwin32 vs regular GNU
15 Jan 1998 03:57:51 -0800
Message-ID: <199801140224.SAA02484.cygnus.gnu-win32@skaro.cygnus.com>
References: <199801091209 DOT NAA27178 AT gevrey DOT ixi DOT fr>
Content-Type: text
To: thierry DOT parmentelat AT ixi DOT fr (Thierry Parmentelat)
Cc: fjh AT cs DOT mu DOT OZ DOT AU, thierry DOT parmentelat AT ixi DOT fr, gnu-win32 AT cygnus DOT com

Thierry Parmentelat wrote:
[...]
> This raises a wider matter: what is the policy of cygwin32, in terms
> of convergence/divergence with the initial GNU tools ?
> I mean, will the patches made by the cygwin32 team on a given gnu tool,
> be incorporated in the standard (MIT) distribution one day ?
> 
> I understand it is more convenient for cygnus to handle a complete
> set of tools, but for guys like me who need only a (potentially very)
> small part of the whole rot, it would be great if we could pick it
> on its own somewhere.

Divergence should be avoided whenever possible.  At this point there is a
set of patches to many of the tools for Cygwin32 as most of you know.
We are (or will be) working with the maintainers of the various tools
to integrate Cygwin32 support.  The next release of bash will come with
Cygwin32 support for example.  It may be some time before all packages
are dealt with though...

-- 
Geoffrey Noer
noer AT cygnus DOT com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".