* Re: [Emacs-diffs] /srv/bzr/emacs/trunk r101037: * configure.in (AC_PREREQ): Require autoconf 2.66 to stop version churn.
[not found] <E1OiYmk-0003bF-VL@internal.in.savannah.gnu.org>
@ 2010-08-10 10:42 ` Stefan Monnier
2010-08-10 12:07 ` Dan Nicolaescu
0 siblings, 1 reply; 3+ messages in thread
From: Stefan Monnier @ 2010-08-10 10:42 UTC (permalink / raw)
To: Dan Nicolaescu; +Cc: emacs-devel
> * configure.in (AC_PREREQ): Require autoconf 2.66 to stop version churn.
What means "version churn" and why is it a problem?
Debian testing still isn't up to 2.66, so I think it's kind of early to
move away from 2.65.
Stefan
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [Emacs-diffs] /srv/bzr/emacs/trunk r101037: * configure.in (AC_PREREQ): Require autoconf 2.66 to stop version churn.
2010-08-10 10:42 ` [Emacs-diffs] /srv/bzr/emacs/trunk r101037: * configure.in (AC_PREREQ): Require autoconf 2.66 to stop version churn Stefan Monnier
@ 2010-08-10 12:07 ` Dan Nicolaescu
2010-08-10 13:40 ` Stefan Monnier
0 siblings, 1 reply; 3+ messages in thread
From: Dan Nicolaescu @ 2010-08-10 12:07 UTC (permalink / raw)
To: Stefan Monnier; +Cc: emacs-devel
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> * configure.in (AC_PREREQ): Require autoconf 2.66 to stop version churn.
>
> What means "version churn" and why is it a problem?
When regenerating configure in the past few days 2.65 and 2.66 where
used alternatively a few times. The large diffs generated each time
make it hard to verify that the change did not have unintended
consequences.
> Debian testing still isn't up to 2.66, so I think it's kind of early to
> move away from 2.65.
I had to install 2.66 locally too (replacing 2.65 that I also had
installed locally). It takes about 5 seconds to install, so...
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Emacs-diffs] /srv/bzr/emacs/trunk r101037: * configure.in (AC_PREREQ): Require autoconf 2.66 to stop version churn.
2010-08-10 12:07 ` Dan Nicolaescu
@ 2010-08-10 13:40 ` Stefan Monnier
0 siblings, 0 replies; 3+ messages in thread
From: Stefan Monnier @ 2010-08-10 13:40 UTC (permalink / raw)
To: Dan Nicolaescu; +Cc: emacs-devel
>> What means "version churn" and why is it a problem?
> When regenerating configure in the past few days 2.65 and 2.66 where
> used alternatively a few times. The large diffs generated each time
> make it hard to verify that the change did not have unintended
> consequences.
I think that's a rather minor issue compared to the problem of developers
not being able to regenerate `configure'.
> I had to install 2.66 locally too (replacing 2.65 that I also had
> installed locally). It takes about 5 seconds to install, so...
That's a good hint that it's on the wrong side of bleeding edge.
Could you please revert this change until distributions like Debian
testing update their packages?
Stefan
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-08-10 13:40 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <E1OiYmk-0003bF-VL@internal.in.savannah.gnu.org>
2010-08-10 10:42 ` [Emacs-diffs] /srv/bzr/emacs/trunk r101037: * configure.in (AC_PREREQ): Require autoconf 2.66 to stop version churn Stefan Monnier
2010-08-10 12:07 ` Dan Nicolaescu
2010-08-10 13:40 ` Stefan Monnier
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.