unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Patch to INSTALL.CVS to clarify why `make bootstrap'	sometimes	fails.
Date: Sun, 08 Jun 2008 12:00:25 +0300	[thread overview]
Message-ID: <uy75gl2s6.fsf@gnu.org> (raw)
In-Reply-To: <858wxgba2c.fsf@lola.goethe.zz>

> From: David Kastrup <dak@gnu.org>
> Date: Sun, 08 Jun 2008 10:33:15 +0200
> Cc: acm@muc.de, monnier@iro.umontreal.ca, emacs-devel@gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > What I described above is common for _all_ targets in the Makefile.
> > That's how Make works, so deliberately disrupting that to such an
> > extreme degree as suggested here would unpleasantly surprise users.
> 
> Do you really think that it is common for typical users to habitually
> fix bootstrap errors and continue, to a degree where they get annoyed
> when this process loses them 10 minutes "each time"?

It's common for those who habitually use "make bootstrap".  And 10
minutes can be as much as 30 on slower machines, which isn't fun at
all.

> And they won't, in all their annoyance, read the docs or Makefile
> and discover "bootstrap-continue"?  I find that hard to believe.

IMO, it's a bad mantra to go against user expectations, even if they
are documented.

> Anyway, how about including my repeated suggestion of a
> "bootstrap-clean" target in your browbeating

You don't need me to include it.

> while you are standing up for the status quo?

Not for status quo, for knowing thy tools, and for personal
soul-searching _before_ blaming ``broken tools'' and ``broken build
processes''.




  reply	other threads:[~2008-06-08  9:00 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-07 10:14 Patch to INSTALL.CVS to clarify why `make bootstrap' sometimes fails Alan Mackenzie
2008-06-07 11:58 ` Eli Zaretskii
2008-06-07 18:40 ` Stefan Monnier
2008-06-07 19:09   ` Miles Bader
2008-06-07 20:17     ` Stefan Monnier
2008-06-07 19:57   ` Glenn Morris
2008-06-07 20:20   ` Eli Zaretskii
2008-06-07 20:52     ` David Kastrup
2008-06-07 21:14       ` Eli Zaretskii
2008-06-07 22:22         ` David Kastrup
2008-06-08  6:42           ` Eli Zaretskii
2008-06-08  8:33             ` David Kastrup
2008-06-08  9:00               ` Eli Zaretskii [this message]
2008-06-08  9:32                 ` David Kastrup
2008-06-08 19:01                 ` Glenn Morris
2008-06-08  2:46       ` Eric Hanchrow
2008-06-08  3:28         ` Stefan Monnier
2008-06-08  5:38           ` Stephen J. Turnbull
2008-06-08  8:21       ` Richard M Stallman
2008-06-08  3:03     ` Stefan Monnier
2008-06-08  8:05   ` Alan Mackenzie
2008-06-09  1:08     ` Stefan Monnier
2008-06-07 19:55 ` Glenn Morris

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=uy75gl2s6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).