From: Zefram <zefram@fysh.org>
To: Bart Schaefer <schaefer@candle.brasslantern.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: PATCH: Re: zsh and autoconf-2.50
Date: Mon, 4 Jun 2001 08:36:27 +0100 (BST) [thread overview]
Message-ID: <E156ouZ-00047x-00@crucigera.fysh.org> (raw)
In-Reply-To: <1010603184301.ZM30412@candle.brasslantern.com> from Bart Schaefer at "Jun 3, 2001 06:43:01 pm"
Bart Schaefer wrote:
>I suggest this because, upon further consideration, I don't want to
>require zsh developers to install autoconf 2.50. They may need the
>older version of autoconf for other packages that have not been updated
>for the 2.50 changes.
>
>Thoughts?
Cute technique. But previously we have never attempted to maintain
compatibility with more than one version of autoconf; we have always had
a flag day where all developers have had to switch to the new version, and
it has never been a problem. When dealing with packages as convoluted as
ours, such as to require a specific version of autoconf, it does not seem
too much of a burden for developers (specifically, developers that modify
the configure source) to marshall more than one version of autoconf.
I'm glad we won't need that config.status kludge any more.
-zefram
next prev parent reply other threads:[~2001-06-04 7:36 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-30 21:48 Jos Backus
2001-05-30 22:02 ` Bart Schaefer
2001-05-30 22:28 ` Jos Backus
2001-05-30 22:40 ` Clint Adams
2001-05-31 0:08 ` Bart Schaefer
2001-05-31 13:40 ` Clint Adams
2001-05-31 13:53 ` Oliver Kiddle
2001-05-31 14:24 ` Clint Adams
2001-05-31 17:34 ` Akim Demaille
2001-05-31 17:51 ` Clint Adams
2001-05-31 18:01 ` Akim Demaille
2001-06-01 8:55 ` Andrej Borsenkow
2001-06-01 11:00 ` Akim Demaille
2001-06-01 16:48 ` Tim Van Holder
2001-06-01 9:37 ` Peter Stephenson
2001-06-01 12:27 ` Clint Adams
2001-06-01 12:45 ` Peter Stephenson
2001-06-01 12:54 ` Andrej Borsenkow
2001-06-01 13:33 ` Peter Stephenson
2001-06-01 13:47 ` Bart Schaefer
2001-06-01 13:56 ` Peter Stephenson
2001-06-01 13:57 ` Andrej Borsenkow
2001-06-01 14:05 ` Andrej Borsenkow
2001-06-01 14:08 ` Clint Adams
2001-06-01 14:19 ` Andrej Borsenkow
2001-06-01 14:25 ` Peter Stephenson
2001-06-01 14:36 ` Andrej Borsenkow
2001-06-01 15:05 ` Clint Adams
2001-06-01 22:31 ` PATCH: " Andrej Borsenkow
2001-06-03 18:43 ` Bart Schaefer
2001-06-03 19:20 ` Clint Adams
2001-06-04 7:36 ` Zefram [this message]
2001-06-04 8:55 ` Bart Schaefer
2001-06-04 9:45 ` Andrej Borsenkow
2001-06-06 8:45 ` Commited: " Andrej Borsenkow
2001-06-06 9:44 ` Peter Stephenson
2001-06-06 10:54 ` Bart Schaefer
2001-06-06 11:02 ` Andrej Borsenkow
2001-06-06 10:58 ` Andrej Borsenkow
2001-06-06 11:23 ` Akim Demaille
2001-06-06 11:34 ` Andrej Borsenkow
2001-06-06 12:45 ` Akim Demaille
2001-06-06 12:35 ` Andrej Borsenkow
2001-06-06 11:06 ` Bart Schaefer
2001-06-06 11:15 ` Andrej Borsenkow
2001-06-01 14:19 ` Peter Stephenson
2001-06-01 14:11 ` Peter Stephenson
2001-05-30 22:34 ` Clint Adams
2001-05-30 22:44 ` Jos Backus
2001-05-31 8:25 ` Andrej Borsenkow
2001-05-31 13:44 ` Clint Adams
2001-05-31 13:59 ` Andrej Borsenkow
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E156ouZ-00047x-00@crucigera.fysh.org \
--to=zefram@fysh.org \
--cc=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).