* autogen.sh question
@ 2005-09-25 20:50 Marcin Antczak
2005-09-25 21:36 ` Thien-Thi Nguyen
0 siblings, 1 reply; 6+ messages in thread
From: Marcin Antczak @ 2005-09-25 20:50 UTC (permalink / raw)
Hi!
Could someone explain to me why there is no 'usual' ./autogen.sh file in
emacs cvs?
And why there is ./configure in cvs instead of just ./configure.in?
I want to apply a patch to ./configure (debian-rpath workaround) and I
wonder if should I apply this patch to ./configure or to ./configure.in
and regenerate ./configure with autogen after applying patch
to ./configure.in.
Marcin
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: autogen.sh question
2005-09-25 20:50 autogen.sh question Marcin Antczak
@ 2005-09-25 21:36 ` Thien-Thi Nguyen
2005-09-25 22:29 ` Paul Pogonyshev
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Thien-Thi Nguyen @ 2005-09-25 21:36 UTC (permalink / raw)
Cc: emacs-devel
Marcin Antczak <marcin.antczak@orange.pl> 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 to use autoconf but not
automake, so if an autogen.sh were ever to be introduced its sole
command would be to run autoconf. probably not worth the trouble.
> 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.
> I want to apply a patch to ./configure (debian-rpath workaround)
> and I wonder if should I apply this patch to ./configure or to
> ./configure.in and regenerate ./configure with autogen after
> applying patch to ./configure.in.
configure.in is the source, so the patch should be applied there.
the top-level ChangeLog gives a hint about the practice: 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.
in the ChangeLog, however, i recorded both edits in one entry.
thi
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: autogen.sh question
2005-09-25 21:36 ` Thien-Thi Nguyen
@ 2005-09-25 22:29 ` Paul Pogonyshev
2005-09-26 0:45 ` Daniel Brockman
2005-09-26 3:47 ` Eli Zaretskii
2 siblings, 0 replies; 6+ messages in thread
From: Paul Pogonyshev @ 2005-09-25 22:29 UTC (permalink / raw)
Cc: emacs-devel
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
successfully run `autogen.sh' for a person not involved in project
is very low and tends to zero as project size increases. I think
it is important that `configure' is in CVS _especially_ for a
project with such a slow release cycle as Emacs has. I always
use CVS Emacs and I'm very happy with not having to run some
specific version of Autoconf.
Paul
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: autogen.sh question
2005-09-25 21:36 ` Thien-Thi Nguyen
2005-09-25 22:29 ` Paul Pogonyshev
@ 2005-09-26 0:45 ` Daniel Brockman
2005-09-26 10:53 ` Thien-Thi Nguyen
2005-09-26 3:47 ` Eli Zaretskii
2 siblings, 1 reply; 6+ messages in thread
From: Daniel Brockman @ 2005-09-26 0:45 UTC (permalink / raw)
Thien-Thi Nguyen <ttn@gnu.org> 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 `configure'?
--
Daniel Brockman <daniel@brockman.se>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: autogen.sh question
2005-09-26 0:45 ` Daniel Brockman
@ 2005-09-26 10:53 ` Thien-Thi Nguyen
0 siblings, 0 replies; 6+ messages in thread
From: Thien-Thi Nguyen @ 2005-09-26 10:53 UTC (permalink / raw)
Cc: emacs-devel
Daniel Brockman <daniel@brockman.se> 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 to ensure timestamps of freshly checked out files to be in order
of configure.in older than configure.
(my confusion runs deep, but the practice is (apparently) harmless.)
thi
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: autogen.sh question
2005-09-25 21:36 ` Thien-Thi Nguyen
2005-09-25 22:29 ` Paul Pogonyshev
2005-09-26 0:45 ` Daniel Brockman
@ 2005-09-26 3:47 ` Eli Zaretskii
2 siblings, 0 replies; 6+ messages in thread
From: Eli Zaretskii @ 2005-09-26 3:47 UTC (permalink / raw)
Cc: marcin.antczak, emacs-devel
> From: Thien-Thi Nguyen <ttn@gnu.org>
> 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 another
file that needs to be remade (with `autoheader') whenever configure.in
changes.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2005-09-26 10:53 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-09-25 20:50 autogen.sh question Marcin Antczak
2005-09-25 21:36 ` Thien-Thi Nguyen
2005-09-25 22:29 ` Paul Pogonyshev
2005-09-26 0:45 ` Daniel Brockman
2005-09-26 10:53 ` Thien-Thi Nguyen
2005-09-26 3:47 ` Eli Zaretskii
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.