Mail Archives: cygwin/2006/07/26/15:51:18
On Wed, 26 Jul 2006, William Sheehan wrote:
> I have been following this discussion closely, as we were also hit by
> this change. However, in all the emails and the ChangeLog, I still
> can't find an official reason why the change was made in the first
> place. Was it for technical reasons? And if so, would the Cygwin team
> accept a patch that readded win32 path support? Or was it for
> idealistic reasons?
>
> Thanks for any replies; I am genuinely curious about the official
> reason.
The official reason, as stated by the maintainer, was that he was tired of
maintaining an out-of-tree patch (which is also why it doesn't appear in
the official upstream ChangeLog). It's not Cygwin that needs to be
patched, it's make. Try making the above pitch to the make maintainers
(on the GNU make list or through Savannah -- see
<http://gnu.org/software/make/>). If the vanilla make sources start
supporting Win32 paths in Cygwin, with someone else providing and
maintaining this functionality upstream, I'm sure the Cygwin make package
maintainer will not go out of his way to remove this support.
HTH,
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`' -. ;-;;,_ Igor Peshansky, Ph.D. (name changed!)
|,4- ) )-,_. ,\ ( `'-' old name: Igor Pechtchanski
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -