unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, handa@m17n.org
Subject: Re: BZR and the bootstrap
Date: Tue, 10 Aug 2010 20:26:00 +0300	[thread overview]
Message-ID: <83k4nyv0pj.fsf@gnu.org> (raw)
In-Reply-To: <jwvpqxqkeq1.fsf-monnier+emacs@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org
> Date: Tue, 10 Aug 2010 11:20:57 +0200
> 
> > I think just turning off VC-facility while building is good.
> > Are there any merit in having it while building?
> 
> I don't think VC brings any benefits while building Emacs, indeed.

Nevertheless, I don't like the idea of turning it off in some
circumstances.  From the moment we made VC an inherent part of
visiting files, it should do that always, because this is now a
routine part of file ops.  If we disable it in some situations, a Lisp
programmer will be unable to tell when VC is available and when not
without consulting the code or the docs, because no one will remember
all these conditions a year from now.

> OTOH, if it needs to be turned off in this case, maybe it needs to be
> turned off in other cases.  IOW, I'd rather try and make sure VC "never"
> needs to be turned off, or only in cases where the user really has an
> odd config that justifies such a measure.

Right.

> E.g. we could change VC so it figures out which backend is in use
> (etc...) more lazily.

I think the problem here is with running "bzr status".  But we could
be smarter about doing that in a lightweight checkout.



  reply	other threads:[~2010-08-10 17:26 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-07 16:49 BZR and the bootstrap Angelo Graziosi
2010-08-09  2:55 ` Eli Zaretskii
2010-08-09  3:37   ` Óscar Fuentes
2010-08-09  6:57     ` Stephen J. Turnbull
2010-08-09  8:57       ` Angelo Graziosi
2010-08-09  9:52         ` Angelo Graziosi
2010-08-09 10:59           ` Óscar Fuentes
2010-08-09 11:53             ` Stephen J. Turnbull
2010-08-09 10:57       ` Óscar Fuentes
2010-08-09 11:57         ` Stephen J. Turnbull
2010-08-09 17:12           ` Eli Zaretskii
2010-08-09 17:11       ` Eli Zaretskii
2010-08-09 21:47         ` Angelo Graziosi
2010-08-09 21:59           ` Óscar Fuentes
2010-08-09 19:42   ` Johan Bockgård
2010-08-10  6:19     ` Eli Zaretskii
2010-08-10  7:32       ` Kenichi Handa
2010-08-10  9:20         ` Stefan Monnier
2010-08-10 17:26           ` Eli Zaretskii [this message]
2010-08-10  7:27     ` Stefan Monnier

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=83k4nyv0pj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.org \
    --cc=monnier@iro.umontreal.ca \
    /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).