all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: bob@gnu.org (Robert J. Chassell)
To: Karl Fogel <kfogel@red-bean.com>
Cc: bob@gnu.org, emacs-devel@gnu.org
Subject: Re: bazaar: "unable to obtain lock"
Date: Thu, 31 Dec 2009 19:19:05 -0500	[thread overview]
Message-ID: <E1NQVEP-0005M1-OH@fencepost.gnu.org> (raw)
In-Reply-To: <87fx6rc5wg.fsf@red-bean.com> (message from Karl Fogel on Thu, 31 Dec 2009 14:14:39 -0500)

    I wrote:

        Next I am going to bootstrap it with the
        changes I got with a `bzr pull'.

        How do I avoid a shell and do it all in Emacs?

Karl Fogel <kfogel@red-bean.com> wrote:

    Oops, I'm not quite sure what the question is -- what's the "it" here?
    Compile Emacs?  Update your local sources using bzr?  

Both, using Emacs scripts such as these two (for the emacs/trunk/
directory):

    (progn
      (cd "/usr/local/src/emacs/trunk")
      (compile
       "time make -k -C lisp autoloads \
        EMACS=/usr/local/src/emacs/trunk/src/emacs && \
        cd lisp && \
        time make EMACS=/usr/local/src/emacs/trunk/src/emacs && \
        cd /usr/local/src/emacs/trunk && \
        time make info html"))

;; and

    (progn
      (cd "/usr/local/src/emacs/trunk/")
      (compile "time make -k"))

(This succeeded this morning, as did the bootstrap which I did in a BASH
shell yesterday.)

I want to update my Emacs each day and build the current Emacs.  Perhaps
the updating and the building will be in different directories, perhaps
not.  (I hope through use to continue testing Emacs every day.)

Also, I want to find out how to shift from the current emacs/trunk/
directory to an emacs/ directory without having to download again and
with the trunk/ and quickfixes/ directory under the emacs/ directory.
My .emacs file and my Emacs scripts have many instances of
"/usr/local/src/emacs/" in them; besides, the emacs/ directory is a good
place to put the sources and compiled files of Emacs.  

Óscar Fuentes suggested using `bzr init-repo <name-of-new-directory>'
and branch rather than the `cp -R' that I had been using before.  (He
also suggested using bind, which I have already done in the
"/usr/local/src/emacs/trunk/" directory.)  Suggesting I use init-repo
is good.  I stay on my own machine.  I would thank James Cloos, too,
except the emacs/src/ directory contains C code.  I really want to
move most of the Emacs code into and below the "/usr/local/src/emacs/"
directory with the C code in the emacs/src/ directory and the Emacs
Lisp in the emacs/lisp/ directory.

The emacs/src/ directory should be directly below the emacs/ directory
and I should rebuild the emacs executable in the emacs/src directory
every day.  The lisp/ directory should be directly below the emacs/
directory, too, not separated, as it is now, by the trunk/ directory.
In addition, I would like the trunk/ and quickfixes/ directories to be
directly below the emacs/ directory as they are now, but that is not so
important.  I do not care where the .bzr/ directories are, nor where I
build.  But the main sources (and executables) should be in and under
the "/usr/local/src/emacs/" directory.  That makes sense when you speak
of the `emacs/lisp/mail' directory.  Otherwise, all of us will have to
change our language to say the `emacs/trunk/lisp/mail' directory.
Doubtless among all of you, I will figure this out.  At the moment, I
don't dare use cp or mv.  Perhaps I should use init-repo and branch to
make a copy and update instead of pull.  Please tell me what to do.

Thank you.

-- 
    Robert J. Chassell                          
    bob@gnu.org                                 bob@rattlesnake.com
    http://www.rattlesnake.com                  http://www.teak.cc




  reply	other threads:[~2010-01-01  0:19 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-29 23:53 bazaar: "unable to obtain lock" Robert J. Chassell
2009-12-30  3:39 ` Karl Fogel
2009-12-30 15:15   ` Robert J. Chassell
2009-12-31 19:14     ` Karl Fogel
2010-01-01  0:19       ` Robert J. Chassell [this message]
2009-12-31 19:15     ` Karl Fogel
2009-12-30 16:43   ` Robert J. Chassell
2009-12-30 17:25     ` Andreas Schwab
2009-12-30 21:46       ` Robert J. Chassell
2009-12-30 22:18         ` Andreas Schwab
2009-12-31  1:48           ` Robert J. Chassell
2009-12-31  4:29             ` Óscar Fuentes
2009-12-31  6:59               ` Óscar Fuentes
2009-12-31 11:32               ` Robert J. Chassell
2009-12-31 14:57                 ` James Cloos
2009-12-30 23:34   ` Kevin Ryde
2009-12-31  0:30     ` Óscar Fuentes
2009-12-31  0:44       ` Lennart Borgman
2009-12-31  1:07         ` Óscar Fuentes
2009-12-31  1:24           ` Lennart Borgman
2010-01-03 22:38       ` Kevin Ryde
2010-01-04  7:05         ` Eli Zaretskii
2010-01-05 21:20           ` Kevin Ryde
2010-01-01  9:59     ` Stephen J. Turnbull
2010-01-01 10:16       ` Óscar Fuentes
2010-01-01 16:42       ` Jason Earl
2009-12-30  9:19 ` David Kastrup
  -- strict thread matches above, loose matches on Subject: below --
2009-12-29 17:14 Juanma Barranquero
2009-12-29 17:40 ` Karl Fogel
2009-12-29 17:44   ` Juanma Barranquero
2009-12-29 18:42     ` Karl Fogel
2009-12-29 20:39       ` Juanma Barranquero

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=E1NQVEP-0005M1-OH@fencepost.gnu.org \
    --to=bob@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=kfogel@red-bean.com \
    /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.