From: chad <yandros@MIT.EDU>
To: rms@gnu.org, "emacs-devel@gnu.org Development" <emacs-devel@gnu.org>
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Bootstrap deleted DOC-nnn file
Date: Fri, 10 May 2013 15:33:00 -0700 [thread overview]
Message-ID: <F9334A53-FDCE-40E6-ACFC-A2146966917C@mit.edu> (raw)
In-Reply-To: <E1UavUB-0006kC-D5@fencepost.gnu.org>
On 10 May 2013, at 15:08, Richard Stallman <rms@gnu.org> wrote:
> But "make bootstrap" also deletes all the emacs-nnn executables,
> doesn't it? If so, there's no point in keeping their DOC files.
>
> Yes there is. I had a job running, and it could not get its DOC file.
>
> However, it is a bad thing to delete the old executables too.
> It is sometimes useful to compare behavior of the new version
> with the old version. There is no need to delete them,
> so let the user decide.
I used to run into this minor issue frequently when building
development versions of emacs for MIT's campus computer system.
Over time, the build trees would collect a bunch of DOC files, but
it was pretty easy to clean up, and since we were intentionally on
the bleeding edge, keeping multiple versions was occasionally useful.
There is a big problem with that approach, though: only the executable
and the DOC files are versioned. The elisp libraries would immediately
out of sync, and since most of the changes are to lisp files, the
old binary+DOC was of very limited usefulness.
As an aside, these days I follow emacs dev on a macosx system (using
the ns port; the mac port doesn't have this functionality) that
uses a relocatable install, so the entirety of emacs lives inside
a single emacs-only directory tree (Emacs.app). This makes multiple
versions very easy to manage, and I keep at least two independent
emacsen around at all times. It's saved me more than once.
I hope that helps,
~Chad
next prev parent reply other threads:[~2013-05-10 22:33 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 0:22 Bootstrap deleted DOC-nnn file Richard Stallman
2013-05-10 9:24 ` Eli Zaretskii
2013-05-10 11:02 ` Stephen J. Turnbull
2013-05-10 12:51 ` Eli Zaretskii
2013-05-10 17:01 ` Stephen J. Turnbull
2013-05-10 17:19 ` Eli Zaretskii
2013-05-11 2:46 ` Stephen J. Turnbull
2013-05-10 22:08 ` Richard Stallman
2013-05-10 22:33 ` chad [this message]
2013-05-11 3:09 ` Stephen J. Turnbull
2013-05-11 12:10 ` Richard Stallman
2013-05-11 16:49 ` Richard Stallman
2013-05-11 17:16 ` Eli Zaretskii
2013-05-11 21:44 ` Richard Stallman
2013-05-11 22:14 ` Christopher Schmidt
2013-05-12 19:39 ` Richard Stallman
2013-05-12 3:00 ` Eli Zaretskii
2013-05-12 19:39 ` Richard Stallman
2013-05-12 20:00 ` Eli Zaretskii
2013-05-13 14:09 ` Richard Stallman
2013-05-13 16:27 ` Andreas Schwab
2013-05-14 13:32 ` Richard Stallman
2013-05-14 16:32 ` Paul Eggert
2013-05-15 11:43 ` Richard Stallman
2013-05-15 12:22 ` Eli Zaretskii
2013-05-15 13:24 ` Xue Fuqiao
2013-05-15 23:27 ` Richard Stallman
2013-05-15 19:08 ` Stefan Monnier
2013-05-15 22:37 ` Xue Fuqiao
2013-05-14 16:54 ` Andreas Schwab
2013-05-15 11:43 ` Richard Stallman
2013-05-15 12:20 ` Eli Zaretskii
2013-05-15 23:27 ` Richard Stallman
2013-05-13 16:30 ` Eli Zaretskii
2013-05-12 2:45 ` Stephen J. Turnbull
2013-05-12 15:33 ` Eli Zaretskii
2013-05-12 19:39 ` Richard Stallman
2013-05-12 19:39 ` Richard Stallman
2013-05-12 23:32 ` Stephen J. Turnbull
2013-05-13 23:47 ` Richard Stallman
2013-05-14 1:24 ` Stephen J. Turnbull
2013-05-12 19:39 ` Richard Stallman
2013-05-12 23:04 ` Stephen J. Turnbull
2013-05-11 7:13 ` Eli Zaretskii
2013-05-11 12:10 ` Richard Stallman
2013-05-11 12:58 ` Eli Zaretskii
2013-05-11 14:50 ` Stefan Monnier
2013-05-11 16:49 ` Richard Stallman
2013-05-11 17:37 ` Stefan Monnier
2013-05-11 21:44 ` Richard Stallman
2013-05-13 15:15 ` Stefan Monnier
2013-05-13 23:47 ` Richard Stallman
2013-05-14 1:56 ` Stefan Monnier
2013-05-14 6:29 ` Eli Zaretskii
2013-05-14 12:48 ` Stefan Monnier
2013-05-15 0:05 ` Richard Stallman
2013-05-11 16:49 ` Richard Stallman
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=F9334A53-FDCE-40E6-ACFC-A2146966917C@mit.edu \
--to=yandros@mit.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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.