unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>, emacs-devel@gnu.org
Subject: Re: /srv/bzr/emacs/trunk r103850: update_autogen
Date: Fri, 08 Apr 2011 12:09:30 -0400	[thread overview]
Message-ID: <87ei5crah1.fsf@stupidchicken.com> (raw)
In-Reply-To: <4D9EAF8C.70303@cs.ucla.edu> (Paul Eggert's message of "Thu, 07 Apr 2011 23:47:40 -0700")

Paul Eggert <eggert@cs.ucla.edu> writes:

> On 04/07/2011 09:16 PM, Stephen J. Turnbull wrote:
>> Paul Eggert writes:
>>
>>  > But why not use the latest Autoconf version in the cron job?
>>  > I don't see the downside.
>>
>> People will depend on the cron job, and neologisms will creep in.
>
> (shrug)  I don't see that as something requiring us to use old tools
> when we generate software.  If someone inadvertently puts in
> something that requires Autoconf 2.68, then we can yank it out,
> just as we yank out code requiring GNU Make 3.82 or GCC 4.6.0 or whatever.
>
> Again, for maintainers it's no big deal.  I just hope that when we
> cut tarballs for non-maintainers that we use the better tools.

IIRC, in the past we've encountered Autoconf bugs going both ways
(i.e. in versions that are new and versions that are old).  When we
begin pretesting Emacs 24, we will want to pick one Autoconf version and
stick to it, unless/until a specific problem is found with that version.

But at the moment the choice of Autoconf version probably doesn't
matter.



  reply	other threads:[~2011-04-08 16:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1Q7YEZ-0005TE-HZ@colonialone.fsf.org>
2011-04-07  2:18 ` /srv/bzr/emacs/trunk r103850: update_autogen Glenn Morris
2011-04-07  5:03   ` Paul Eggert
2011-04-07 16:28     ` Glenn Morris
2011-04-07 18:26       ` Paul Eggert
2011-04-08  0:08         ` Glenn Morris
2011-04-08  2:04           ` Paul Eggert
2011-04-08  4:16             ` Stephen J. Turnbull
2011-04-08  6:47               ` Paul Eggert
2011-04-08 16:09                 ` Chong Yidong [this message]
2011-04-09  1:29         ` Stefan Monnier
2011-04-09 17:50           ` Paul Eggert

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ei5crah1.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@gnu.org \
    --cc=stephen@xemacs.org \
    /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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).