From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tim Cross Newsgroups: gmane.emacs.devel Subject: Re: New build process? Date: Wed, 27 Jul 2011 13:40:03 +1000 Message-ID: References: <20110726184220.GA6390@acm.acm> <87bowg6fre.fsf@fencepost.gnu.org> <4E2F2084.7070001@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: dough.gmane.org 1311738015 31293 80.91.229.12 (27 Jul 2011 03:40:15 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 27 Jul 2011 03:40:15 +0000 (UTC) Cc: david.reitter@gmail.com, Daniel Colascione , emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Jul 27 05:40:11 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Qluyg-0001T5-Mm for ged-emacs-devel@m.gmane.org; Wed, 27 Jul 2011 05:40:10 +0200 Original-Received: from localhost ([::1]:37125 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qluyg-0007On-5x for ged-emacs-devel@m.gmane.org; Tue, 26 Jul 2011 23:40:10 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:52740) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qluyd-0007Mi-7n for emacs-devel@gnu.org; Tue, 26 Jul 2011 23:40:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qluyc-00056P-6M for emacs-devel@gnu.org; Tue, 26 Jul 2011 23:40:07 -0400 Original-Received: from mail-iy0-f169.google.com ([209.85.210.169]:35736) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qluya-00054D-QN; Tue, 26 Jul 2011 23:40:04 -0400 Original-Received: by iyb14 with SMTP id 14so1611476iyb.0 for ; Tue, 26 Jul 2011 20:40:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=c66uLXEs7nUjfUPdWTKxrtszmHt+yqlFMjmY+qomPYg=; b=ODAEgZiADq2ZClnqKJfxD7CnWWQ4AgpUIKfLD0Jzo0ANqSn/ez37vQL7PCOhYpVJcq VlLxjM50hoAgT53waAs3tUO6Z/GPwYTg8swYCbypWr52+c1DMqJHPwRpNg87JqZ4iuj6 x89Zg6WfHHrqsVSXj9Tt8mvsGugvB3YrUsntw= Original-Received: by 10.231.68.210 with SMTP id w18mr6365459ibi.186.1311738003505; Tue, 26 Jul 2011 20:40:03 -0700 (PDT) Original-Received: by 10.231.37.76 with HTTP; Tue, 26 Jul 2011 20:40:03 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.210.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:142337 Archived-At: On Wed, Jul 27, 2011 at 12:58 PM, Richard Stallman wrote: > =A0 =A0Sure, but having to run autogen.sh on a project that's just been c= hecked out of > =A0 =A0version control is also very common in the free software world, an= d our actual > =A0 =A0source tarballs do contain pre-built autoconf scripts. =A0The prob= lem with a > =A0 =A0self-replacing configure script is that, as you mentioned, it'd be= hard to tell > =A0 =A0bzr to version the placeholder script, but ignore the generated on= e; solving > =A0 =A0this problem by using a nonstandard name for the generated `config= ure' =A0script > =A0 =A0would be surprising. =A0I think our current approach is fine. > > We could call the current configuration script `configure-internal'. > Then have a small `configure' script that checks whether the > `configure-internal' file exists and is up to date, and if not, > generates it. =A0Then it would run `configure-internal'. > > This would DTRT in all cases, wouldn't it? > Lets not over engineer it! As far back as I can remember, emacs sources from the version control repository had an additional step that had to be completed ini order to generate the configure script. Previously, you ran autoget and now you run ./auttogen.sh. Previously, people would get into problems if their autoconf tools werre an older version that supported by the current configs for emacs - the new method now tests to make sure the build tools satisfy version restrictions, which I think is also an improvement. The real issue here is whether INSTALL.BZR is an appropriate name for the information that alerts people that you need to take extra steps when building form sources taken from the version control repository. Perhaps we can come up with a better name - though I'm not sure what. 'build-from -bzr.txt may be too long and won't help those who get the sources form git. I find it hard to judge as I knew about the change after it was announced on this list and didn't have to 'find it' from the doc files, but I can understand how you would miss INSTALL.BZR. Tim