Re: Keeping an ELPA checkout

[Stefan Monnier]

> But ELPA packages are... packages!  Everything in emacs/lisp is source
> code, meant to work as you describe.  Some ELPA packages happen to be
> single-file libraries but you are trying to skip the installation and
> activation steps which track dependencies, byte-compile, and adjust the
> load path.  At least I don't think that's how it is supposed to work in
> Tom Tromey's design.

I know, but I don't think there's any fundamental good reason why we
can't tweak emacs/lisp/Makefile.in so that it gets things to work.

> Which I think are so people can install ELPA locally, edit things
> locally, and reinstall the package when ready.  Does that help?  It can
> probably be automated to be part of a "make local-activate-all" process.

An important part of my use case is that files be used directly from the
Bzr checkout.  Also I don't want to copy any of those files anywhere
near my ~/ or ~/.emacs.d directory: everything should stay cleanly
within the Bzr checkout.


        Stefan