From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: New build process?
Date: Wed, 27 Jul 2011 10:51:29 +0200 [thread overview]
Message-ID: <87aac02jji.fsf@fencepost.gnu.org> (raw)
In-Reply-To: 87sjpsdtaa.fsf@micropit.couberia.bzh
pmlists@free.fr (Peter Münster) writes:
> On Wed, Jul 27 2011, Tim Cross wrote:
>
>> Still, my main pint is I don't think we should get too carried away
>> trying to automate all of this. It is a common requirement and while
>> some may have been caught out, it is something you should expect when
>> working this close to the development layer. Efforts were made to
>> communicate the changes on this list (by you IIRC Eli) and there is
>> information in the INSTALL.BZR file. My objection with trying to
>> automate or eliminate this simple step is that the solution can often
>> be worse than the problem and adds just another point of potential
>> failure in a step which is already simple and straight-forward (once
>> you know about it!).
>
> +1
>
>
>> However, if we can rename the file or make
>> another copy of the instructions under a name which the majority feel
>> is more likely to be noticed, great - all for that.
>
> I don't see a big problem with the file name, but eventually you could
> merge its content into INSTALL and then remove INSTALL.BZR.
INSTALL are the instructions for a user installing from a tarball, so
they should likely not be overly complicated. It does not harm to put a
sentence referring to INSTALL.BZR in, but INSTALL.BZR does not actually
need to be in a tarball.
I actually have a project where INSTALL is autogenerated from something
like doc/install.texi, so there is not even an INSTALL file in the
repository. It is, naturally, in the tarballs.
I think we nowadays distribute INSTALL.CVS along in the tarballs, though
at one time we didn't.
--
David Kastrup
next prev parent reply other threads:[~2011-07-27 8:51 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
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 [this message]
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=87aac02jji.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--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.