From: William G. Gardella <wgg2@member.fsf.org>
To: 15404@debbugs.gnu.org, rms@gnu.org
Subject: bug#15404: Mitigating "make bootstrap" trashing the tree
Date: Wed, 18 Sep 2013 17:16:10 +0000 [thread overview]
Message-ID: <87a9javyn9.fsf@motoko.kusanagi> (raw)
In-Reply-To: <E1VM2ZN-0004wC-SP@fencepost.gnu.org>
Hello,
One suggestion to help avoid "make bootstrap" trashing the source tree
and your old emacs build would be to use "bzr stash" to make a
temporary, local copy of your previous build. Another idea would be to
do something like make install DESTDIR=built-on-`date +%Y-%m-%d_%H-%M`,
so that even if you do not wish to install globally whenever you build
Emacs, you at least have past successful builds in a convenient place.
Ultimately, however, I think "make bootstrap" should avoid doing lots of
implicit things like deleting old builds. It should be reversible
somehow without needing to know bzr hacks or redirect the output of
previous builds. Automated functions that make a mess should clean up
after themselves.
--
Regards,
WGG
next prev parent reply other threads:[~2013-09-18 17:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-17 21:12 bug#15404: make_timespec undefined Richard Stallman
2013-09-17 22:05 ` Glenn Morris
2013-09-18 13:38 ` Richard Stallman
2013-09-18 14:59 ` Eli Zaretskii
2013-09-18 21:51 ` Glenn Morris
2013-09-19 21:18 ` Richard Stallman
2013-09-19 7:09 ` Richard Stallman
2013-09-19 7:33 ` Eli Zaretskii
2013-09-19 7:46 ` Andreas Schwab
2013-09-18 16:19 ` Glenn Morris
2013-09-18 16:22 ` Glenn Morris
2013-09-18 17:31 ` Stefan Monnier
2013-09-18 21:54 ` Glenn Morris
2013-09-19 7:08 ` Richard Stallman
2013-09-19 7:34 ` Eli Zaretskii
2013-09-19 21:18 ` Richard Stallman
2013-09-19 7:40 ` Glenn Morris
2013-09-18 17:16 ` William G. Gardella [this message]
2013-09-18 19:25 ` bug#15404: Mitigating "make bootstrap" trashing the tree Eli Zaretskii
2013-09-18 20:00 ` William G. Gardella
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=87a9javyn9.fsf@motoko.kusanagi \
--to=wgg2@member.fsf.org \
--cc=15404@debbugs.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 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).