This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
Re: Automake 1.4l released
- To: cygwin at Cygwin dot Com
- Subject: Re: Automake 1.4l released
- From: Tom Tromey <tromey at redhat dot com>
- Date: 14 Aug 2001 19:04:11 -0600
- Cc: Cygwin at Cygwin dot Com, Bernard Dautrevaux <Dautrevaux at microprocess dot com>, "'Tim Van Holder'" <tim dot van dot holder at pandora dot be>, automake at gnu dot org
- References: <3B7974C6.83934084@yahoo.com> <3B797B22.C06C71D9@yahoo.com> <87bslip7hj.fsf@creche.redhat.com> <20010814195923.A28367@redhat.com>
- Reply-To: tromey at redhat dot com
>>>>> "Chris" == Christopher Faylor <cgf@redhat.com> writes:
Chris> 1) New version of automake is released with no Cygwin testing
Chris> for an important feature.
True. As far as I know nobody ever tried `make distcheck' on Cygwin
before. In fact this is the first time I've heard of anybody using
Cygwin as their primary maintainer platform for an automake-using
project.
Historically Cygwin has not been an important host platform for
Automake. That seems to be changing though.
Chris> 3) Cygwin people provide workaround which is rejected.
The original suggestion was "disable the feature".
I'd prefer not to do that.
Chris> AFAICT, the rationale for this stance is that Cygwin is a free
Chris> software project and therefore we should just drop everything
Chris> and fix "our bug" if we want automake to work.
Please don't put words in my mouth. Of course I don't think you
should drop anything for this problem. If it is a bug, which I don't
even know for certain, then my preference would be that you prioritize
it along with all the other things that you prioritize.
Chris> Or, possibly, we're supposed to provide a detailed rationale on
Chris> why it isn't possible to fix this in Windows.
Or maybe you could choose not to care that `cp -p' doesn't work.
Chris> This seems to ignore the fact that people are using older
Chris> versions of Cygwin. Is it automake policy to tell people to
Chris> update to newer OS versions when there are problems with
Chris> automake that can be traced to an OS fault? Or, perhaps a
Chris> better example would be, Does the automake group tell people to
Chris> upgrade their libc.so when an incompatibility is detected?
Do you really think I would answer yes to any of these?
If I made you angry, then I'm sorry. I have to say I'm surprised
though. I thought I made my desire clear in my post. For instance, I
said I would consider a workaround in automake as well as preferring
that a real fix be made upstream, either in Cygwin or `cp' as
appropriate. Maybe you prefer otherwise.
Tom
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/