Daniel Brockman <[EMAIL PROTECTED]> writes:
> Why did you wait before checking in `configure'?
superstition from old experience w/ (flaky) cvs over nfs problems
combined w/ automake-influenced (thus, irrelevant in this context)
methodology -- all this from other projects, not emacs. the idea
is
> From: Thien-Thi Nguyen <[EMAIL PROTECTED]>
> Date: 25 Sep 2005 17:36:45 -0400
> Cc: emacs-devel@gnu.org
>
> the top-level ChangeLog gives a hint about the practice: modify
> configure.in, regenerate configure, and check in both files.
Not only configure needs to be regenerated; src/config.in is
Thien-Thi Nguyen <[EMAIL PROTECTED]> writes:
> modify configure.in, regenerate configure, and check in
> both files. when i have done this in the past, i checked
> in configure.in first, waited a few seconds (maybe half a
> minute), and then configure.
Why did you wait before checking in `config
Thien-Thi Nguyen wrote:
> > And why there is ./configure in cvs instead of just
> > ./configure.in?
>
> so that people checking out a source tree from cvs can use the
> ./configure script immediately, w/o having to install autoconf.
From my personal experience I have concluded that the odds to
suc
Marcin Antczak <[EMAIL PROTECTED]> writes:
> Could someone explain to me why there is no 'usual' ./autogen.sh
> file in emacs cvs?
emacs is unusual because its early development preceded that of
the GNU auto* tools (and in some cases even influenced their
design, iirc). at some point emacs began
