From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Thien-Thi Nguyen Newsgroups: gmane.emacs.devel Subject: Re: autogen.sh question Date: 25 Sep 2005 17:36:45 -0400 Message-ID: References: <1127681447.12649.20.camel@localhost.localdomain> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1127685843 7742 80.91.229.2 (25 Sep 2005 22:04:03 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 25 Sep 2005 22:04:03 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Sep 26 00:04:01 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1EJeaO-0005If-P8 for ged-emacs-devel@m.gmane.org; Mon, 26 Sep 2005 00:03:04 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EJeaO-0006U8-9z for ged-emacs-devel@m.gmane.org; Sun, 25 Sep 2005 18:03:04 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1EJeW7-0003qR-TY for emacs-devel@gnu.org; Sun, 25 Sep 2005 17:58:40 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1EJeW5-0003pf-Ci for emacs-devel@gnu.org; Sun, 25 Sep 2005 17:58:38 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1EJeTu-0002Di-66 for emacs-devel@gnu.org; Sun, 25 Sep 2005 17:56:22 -0400 Original-Received: from [207.245.121.137] (helo=mail.agora-net.com) by monty-python.gnu.org with esmtp (TLS-1.0:RSA_ARCFOUR_SHA:16) (Exim 4.34) id 1EJeAw-0006QM-FT for emacs-devel@gnu.org; Sun, 25 Sep 2005 17:36:46 -0400 Original-Received: from ttn by mail.agora-net.com with local (Exim 4.34) id 1EJeAv-0007sf-33; Sun, 25 Sep 2005 17:36:45 -0400 Original-To: Marcin Antczak In-Reply-To: <1127681447.12649.20.camel@localhost.localdomain> Original-Lines: 31 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:43226 Archived-At: Marcin Antczak 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