Re: Keeping an ELPA checkout

[Ted Zlatanov <tzz@lifelogs.com>]

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