all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: New build process?
Date: Wed, 27 Jul 2011 15:56:22 +0200	[thread overview]
Message-ID: <87zkjzzv21.fsf@fencepost.gnu.org> (raw)
In-Reply-To: CANbX364LtwkGxgKOzKrBW1h==izX9kNGQGAWCeDhSF99mbgTmg@mail.gmail.com

Lennart Borgman <lennart.borgman@gmail.com> writes:

> On Wed, Jul 27, 2011 at 15:11, Tim Cross <theophilusx@gmail.com> wrote:
>>>
>>> I'm actually with Richard on this one.  I think the need to install,
>>> update, and use any additional commands before "./configure; make" is
>>> a nuisance whose justification is questionable at best.  It's just
>>> that I gave up on talking people into catering to us dinosaurs whose
>>> paradise was lost, and Richard is still trying, because he's a better
>>> man than I am.
>>>
>>
>> If you believe you can do it and make it solid (which I expect you
>> can), then go for it. I personally don't think it is necessary as we
>> are talking about users who are choosing to interact at a low
>> development level, which IMO is a moving target subject to change and
>> instability. We should not set the bar too high here - put our efforts
>> into improving emacs and not into improving the build process for
>> those who chose to interact at this level.
>>
>> Yes, I guess I would be considered a dinosaur and possibly not even a
>
> Dear dinosaur, can't you believe making the build process simple saves
> a lot of time for many developers?

The build process _is_ simple.  The question is more about it being
discoverable.  Adding two sentences to INSTALL in the line of

    These are the installation instructions for compiling Emacs from a
    distribution tarball.  If you are working from a Bazaar checkout,
    please refer to INSTALL.BZR.

should be enough.

-- 
David Kastrup




  reply	other threads:[~2011-07-27 13:56 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
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 [this message]
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=87zkjzzv21.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.