From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: emacs-devel@gnu.org
Subject: Re: Keeping an ELPA checkout
Date: Tue, 29 Mar 2011 17:16:39 -0400 [thread overview]
Message-ID: <jwvtyel638q.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87pqpage4u.fsf@lifelogs.com> (Ted Zlatanov's message of "Tue, 29 Mar 2011 10:06:25 -0500")
>>> OK. So who's going to do the work? And can you summarize what you're
>>> asking for after this discussion?
SM> What I wrote above is the summary, AFAIK.
> OK, I'll try to summarize because your requirements are not clear to
> me. Tell me if I understand what you're looking for.
You describe a possible solution rather than a requirement ;-)
> 2) check out or update the ELPA branch to $elpa
OK.
> 3) cd $elpa; make local-install EMACS=$trunk/src/emacs (this runs the
> trunk-built Emacs to `package-install' each ELPA package in
> $elpa/packages and then adds "$elpa/packages" to
> `package-directory-list' or maybe gives you a snippet to put in your
> .emacs).
The name "install" is confusing here: I don't want the .el files to
be copied. I just want to compile them, extract their autoloads into
a file somewhere, and things like that.
> The trunk-built Emacs may need to have been installed system-wide.
No, that's undesirable.
> 4) Now all the ELPA packages should be available as if you had installed
> them through `package-install' into ~/.emacs.d because
> `package-directory-list' has been augmented
If you say so.
> 5) any package build and installation artifacts in $elpa need to be
> ignored by Bazaar
Right.
> Is this correct?
I'm not sure, but your point 5 makes me think it is.
Stefan
next prev parent reply other threads:[~2011-03-29 21:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 22:21 Keeping an ELPA checkout Stefan Monnier
2011-03-25 8:19 ` Reiner Steib
2011-03-25 21:09 ` Stefan Monnier
2011-03-25 14:46 ` Ted Zlatanov
2011-03-25 19:52 ` Stefan Monnier
2011-03-25 20:53 ` Ted Zlatanov
2011-03-25 21:06 ` Chong Yidong
2011-03-25 21:16 ` Ted Zlatanov
2011-03-26 19:31 ` Tom Tromey
2011-03-25 21:12 ` Stefan Monnier
2011-03-25 22:02 ` Ted Zlatanov
2011-03-25 23:20 ` Stefan Monnier
2011-03-28 18:38 ` Ted Zlatanov
2011-03-29 1:16 ` Stefan Monnier
2011-03-29 15:06 ` Ted Zlatanov
2011-03-29 21:16 ` Stefan Monnier [this message]
2011-03-30 13:28 ` Ted Zlatanov
2011-03-30 21:29 ` 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=jwvtyel638q.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=tzz@lifelogs.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 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).