all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Daniel Colascione <dan.colascione@gmail.com>
Cc: david.reitter@gmail.com, emacs-devel@gnu.org
Subject: Re: New build process?
Date: Tue, 26 Jul 2011 22:58:01 -0400	[thread overview]
Message-ID: <E1QluJt-0008SP-RQ@fencepost.gnu.org> (raw)
In-Reply-To: <4E2F2084.7070001@gmail.com> (message from Daniel Colascione on Tue, 26 Jul 2011 13:16:04 -0700)

    Sure, but having to run autogen.sh on a project that's just been checked out of
    version control is also very common in the free software world, and our actual
    source tarballs do contain pre-built autoconf scripts.  The problem with a
    self-replacing configure script is that, as you mentioned, it'd be hard to tell
    bzr to version the placeholder script, but ignore the generated one; solving
    this problem by using a nonstandard name for the generated `configure'  script
    would be surprising.  I 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.  Then it would run `configure-internal'.

This would DTRT in all cases, wouldn't it?

-- 
Dr Richard Stallman
President, Free Software Foundation
51 Franklin St
Boston MA 02110
USA
www.fsf.org  www.gnu.org
Skype: No way! That's nonfree (freedom-denying) software.
  Use free telephony http://directory.fsf.org/category/tel/



  reply	other threads:[~2011-07-27  2:58 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 18:42 New build process? Alan Mackenzie
2011-07-26 18:47 ` David Kastrup
2011-07-26 20:00   ` David Reitter
2011-07-26 20:16     ` Daniel Colascione
2011-07-27  2:58       ` Richard Stallman [this message]
2011-07-27  3:40         ` Tim Cross
2011-07-27  5:08           ` Eli Zaretskii
2011-07-27  7:58             ` Tim Cross
2011-07-27  8:25               ` Peter Münster
2011-07-27  8:48                 ` Tim Cross
2011-07-27  9:43                   ` Peter Münster
2011-07-27  8:51                 ` David Kastrup
2011-07-27 10:05                 ` Eli Zaretskii
2011-07-27 10:03               ` Eli Zaretskii
2011-07-27 13:11                 ` Tim Cross
2011-07-27 13:31                   ` Lennart Borgman
2011-07-27 13:56                     ` David Kastrup
2011-07-28 12:37                       ` David De La Harpe Golden
2011-07-28 12:46                         ` David Kastrup
2011-07-29 12:36                           ` Alan Mackenzie
2011-07-27 14:58                     ` Tim Cross
2011-07-27 16:14                 ` Richard Stallman
2011-07-27 16:25                   ` Eli Zaretskii
2011-07-27 20:27                 ` Paul Eggert
2011-07-28 10:06                   ` Eli Zaretskii
2011-07-28 10:15                     ` bug#9106: " Paul Eggert
2011-07-28 16:45                   ` Richard Stallman
2011-07-27  7:51           ` Andreas Schwab
2011-07-27  8:02             ` Tim Cross
2011-07-27  8:07               ` Andreas Schwab
2011-07-27  8:13                 ` Tim Cross
2011-07-27  8:22                   ` Andreas Schwab
2011-07-27  8:31                     ` Tim Cross
2011-07-27  8:54                     ` David Kastrup
2011-07-27  9:01                       ` Andreas Schwab
2011-07-27  9:15                         ` David Kastrup
2011-07-27  9:41                           ` Andreas Schwab
2011-07-26 20:24     ` David Kastrup
2011-07-26 22:10   ` Alan Mackenzie
2011-07-27 12:15     ` Thien-Thi Nguyen

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=E1QluJt-0008SP-RQ@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=dan.colascione@gmail.com \
    --cc=david.reitter@gmail.com \
    --cc=emacs-devel@gnu.org \
    /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.
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.