> I was told over at the autoconf List that I should be using 2.54 because
> 2.53 'is an early alpha release'. I wonder if there are users on List
> here who might have been using a Autoconf-2.54 they've built themselves
> from GNU mainline source?
We're still using 2.53a (or b?), as something i
Actually, Cyg CVS (afaik) determines line termination defauls based on
the cyg dll, and user-defined mounts that the check-out are done to.
I've found this as we have a number of developers using cyg/cvs who have
set up mounts in a number of creative ways (not according to docs,etc.)
... and cvs
> Your suggestion came out fine. It has just been suggested hundreds of
> times in the past.
Ah, I've been lurking on the list for ages - but not noticed the
request. Apologies.
Anyway, would it be worth submitting a patch for the functionality, or
is the dev rather closed?
-mx
signature.
> Eureka! Batch operations!
Oh, heh, my suggestion may not have come out right. I meant something
like: setup --all or --all-dev ... so that one could use setup from the
shell, from a script, remotely, etc.
-mx
signature.asc
Description: This is a digitally signed message part
> How about "Run Cygwin Setup"? It's pretty self-explanatory from then
> on... :-)
You'd actually be suprised ;-P
We use cyg and the Gnu autotools for building our product on Win32 ...
and I find myself walking devs through the effort of setting cyg up (and
then later helping them set it up
5 matches
Mail list logo
