From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: Keeping an ELPA checkout
Date: Wed, 30 Mar 2011 08:28:49 -0500 [thread overview]
Message-ID: <87hbakd9f2.fsf@lifelogs.com> (raw)
In-Reply-To: jwvtyel638q.fsf-monnier+emacs@gnu.org
On Tue, 29 Mar 2011 17:16:39 -0400 Stefan Monnier <monnier@IRO.UMontreal.CA> wrote:
>>>> 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.
SM> You describe a possible solution rather than a requirement ;-)
Yes, I tend to do that :)
>> 2) check out or update the ELPA branch to $elpa
SM> 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).
SM> The name "install" is confusing here: I don't want the .el files to
SM> be copied. I just want to compile them, extract their autoloads into
SM> a file somewhere, and things like that.
I'm pretty sure this will require a `package-install-in-place' function,
after looking at the source. Ugh.
Would "make inplace" be a better name?
>> The trunk-built Emacs may need to have been installed system-wide.
SM> No, that's undesirable.
...so are we then installing in the locally-compiled Emacs (modifying
files under $trunk) or for the user (modifying init/custom files)?
(All this would be much easier if the elpa branch was a subdirectory
under trunk!)
Ted
next prev parent reply other threads:[~2011-03-30 13:28 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
2011-03-30 13:28 ` Ted Zlatanov [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hbakd9f2.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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 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.