This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: Automake 1.4l released -- show of hands from cygwin/automake maintainers?


-- waving my hand --
I am moving most of my software around between Linux, CygWin and DJGPP, and
use Automake for all of them. At the moment, I'm using mostly CygWin, so
yes, I use Automake under CygWin to maintain my software (and yes, I've had
some problems with make distcheck recently, and decided not to support it
for the moment, because I wasn't sure whether the bug was mine or not, and
didn't want to spend too much time finding out)..
I guess when I need a valid distcheck, I'll just move the source to another
platform and bootstrap there.. (for the time being - I'd love a fix of any
known bug, because I don't like bugs)

Greetz!

Ronald

> -----Original Message-----
> From: cygwin-owner@sources.redhat.com
> [mailto:cygwin-owner@sources.redhat.com]On Behalf Of Christopher Faylor
> Sent: Thursday, August 16, 2001 4:14 AM
> To: cygwin@Cygwin.Com
> Subject: Re: Automake 1.4l released -- show of hands from
> cygwin/automake maintainers?
>
>
> [This is for the cygwin mailing list]
> On Wed, Aug 15, 2001 at 08:28:05PM -0600, Tom Tromey wrote:
> >>>>>> "Charles" == Charles Wilson <cwilson@ece.gatech.edu> writes:
> >
> >Charles> Nope.  It actually seems to be due to a change in automake.
> >Charles> Apparently, make distcheck did not previously 'chmod -R a-w'.
> >
> >I looked a bit but due to massive reorganization it is a pain to find
> >out when this went in.
> >
> >
> >We rely on `cp -p' in a few places, all in `dist'.  The problem is
> >most obvious in `distcheck' because it makes the tree read-only when
> >it is unpacked.  But suppose you use something like CVSREAD and check
> >out a tree.  Then a file like configure could very well be read-only,
> >leading to the same problem for a simple `dist'.
> >
> >I think we could add a check for whether "cp -p works in ." to
> >AM_INIT_AUTOMAKE and then use the result everywhere.  For this to work
> >we'd also need to add code to `missing' to handle this case, I think
> >(code I'm not entirely sure how to write -- ideally it would restore
> >the original file's permissions once it was done with the copy).
> >
> >I think our goal should be to support this feature everywhere.  But if
> >there aren't maintainers who need this in 1.5, I would prefer to file
> >a PR and leave it until a later release.  If you are such a
> >maintainer, please speak up.  Charles, are you?
>
> Can we get a show of hands for people who are actually trying to use
> automake as a *maintainer* under cygwin.
>
> I suspect that this is not a big deal and that there is no reason to
> force automake people to waste time on Cygwin's irregularities for
> this release.
>
> If a bunch of people step forward, however, then, obviously I'm wrong.
>
> Again.
>
> So, is anyone using automake in this capacity?  If you don't know what
> I'm talking about then you undoubtedly are not using automake as
> a maintainer.
>
> cgf
>
>
> --
> 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/
>


--
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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]