This is the mail archive of the
cygwin
mailing list for the Cygwin project.
managing autoconf versions?
- From: Jay <jay dot krell at cornell dot edu>
- To: cygwin <cygwin at cygwin dot com>
- Date: Sat, 16 May 2009 06:00:30 +0000
- Subject: managing autoconf versions?
- References: <1242445850.26068.ezmlm@cygwin.com>
This is a little off topic.
How do people manage autoconf/automake versions?
In particular, I'm not doing "my own work" -- I could probably just install one recent version of everything and be ok.
Rather I'm wondering about submitting patches to other projects, some projects might use one set of versions, or another. Change configure.ac/Makefile.am or such and regenerate configure/Makefile.in or such, using a matching toolset version so that churn is only what is desired?
Is the solution to install to various custom prefix and tailor $PATH based on context? Or does one "wrapper" sniff the input or output and decide among the versions installed in a standard place?
You know, like, input/or output could say # use autoconf 1.2.3
and then /usr/bin/autoconf could delegate to /usr/bin/autoconf-1.2.3
or such?
Thanks,
- Jay
--
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/