From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Making a script to update and compile from CVS
Date: Thu, 13 Jan 2005 18:38:06 -0500 [thread overview]
Message-ID: <jwvpt089a8i.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <001801c4f9b8$0cfaacb0$0200a8c0@sedrcw11488> (Lennart Borgman's message of "Thu, 13 Jan 2005 22:36:55 +0100")
> Now I wonder in what order to do this. Should something like this be ok:
Here is what I do, typically:
% tla star-merge OR cvs update
% (cd lisp; make updates recompile)
% if some files failed to compile, (cd lisp; make recompile)
% make
I don't actually do `make install' because I always work directly "in situ",
which is important when I do C-h f so I can click to get to the source and
start editing directly in the Arch/CVS tree.
Sometimes the above fails because the changes require a more
complex bootstrap. In that case, I generally resort to my intuition and
knowledge to come up with an ad-hoc way to bootstrap, and if all else really
fails, I end up resorting to `make bootstrap' but since that takes a long
while I really make every effort to avoid it.
Sometimes the above succeeds but with incorrectly compiled .elc files
(typically because of macros which were not defined when the file was
compiled). I catch those problems "lazily" (i.e. only when and if
I actually use the code).
Stefan
next prev parent reply other threads:[~2005-01-13 23:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 21:36 Making a script to update and compile from CVS Lennart Borgman
2005-01-13 23:34 ` Miles Bader
2005-01-15 0:12 ` Richard Stallman
2005-01-13 23:38 ` Stefan Monnier [this message]
2005-01-14 10:26 ` Kai Großjohann
2005-01-14 19:39 ` Han Boetes
-- strict thread matches above, loose matches on Subject: below --
2005-01-14 12:39 Robert J. Chassell
2005-01-14 18:58 ` Vinicius Jose Latorre
2005-01-14 21:40 ` Michael Albinus
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=jwvpt089a8i.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).