From: Karl Eichwalder <keichwa@gmx.net>
Subject: Re: ./configure
Date: Tue, 31 Jul 2001 01:58:12 +0200 [thread overview]
Message-ID: <shk80qm0kr.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <2n66cal25n.fsf@piglet.jia.vnet> (ShengHuo ZHU's message of "Mon, 30 Jul 2001 11:09:24 -0700")
ShengHuo ZHU <zsh@cs.rochester.edu> writes:
> Stainless Steel Rat <ratinox@peorth.gweep.net> writes:
>
>> * Didier Verna <didier@lrde.epita.fr> on Mon, 30 Jul 2001
>>| Well, you actually *want* to keep configure in CVS because it is no
>>| different from people to people, and it's somewhat insane to make
>>| thousands of people regenerate the *same* file. It also has the advantage
>>| that CVS simple users (not developers) don't have to know autoconf and
>>| friends to build gnus.
Worse: Users/developers might have different version installed. If
you'll not check in automatically generated files you ought to put _all_
devel tools into the CVS -- otherwise you're not able to rebuild stuff
properly.
>> Besides "./autogen.sh" is not that difficult, and it runs configure
>> for you automatically.
Often ./autogen.sh scripts do much to much (calling gettextize every
time).
> Making ./autogen.sh is not difficult and some projects use that, but
> Gnus is different, because we don't change configure.in frequently,
> four times in 3.5 years. In addition, we don't use automake, some
> Gnus users don't have autoconf installed, and ./configure is in both
> the Emacs CVS and the XEmacs CVS. Why we bother?
For quite some time I thought the same. gettext CVS is another
"exception".
--
ke@suse.de (work) / keichwa@gmx.net (home): |
http://www.suse.de/~ke/ | ,__o
Free Translation Project: | _-\_<,
http://www.iro.umontreal.ca/contrib/po/HTML/ | (*)/'(*)
prev parent reply other threads:[~2001-07-30 23:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-19 20:59 ./configure Mattias Ahnberg
2001-07-20 15:09 ` ./configure David Z. Maze
2001-07-20 17:54 ` ./configure ShengHuo ZHU
2001-07-30 8:19 ` ./configure Didier Verna
2001-07-30 14:32 ` ./configure Stainless Steel Rat
2001-07-30 18:09 ` ./configure ShengHuo ZHU
2001-07-30 23:58 ` Karl Eichwalder [this message]
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=shk80qm0kr.fsf@tux.gnu.franken.de \
--to=keichwa@gmx.net \
/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.
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).