I've done some work on implementing bundled ELPA packages. So far I've
not pushed any changes to emacs.git or elpa.git; I'm only changing my
local repositories.

Attached are:

bundle-elpa.diff : changes to master dd4eab759c Sun Feb 14

elpa-policy.diff : changes in emacs/admin/note/elpa since the last time
I posted it.

I'd like some aggreement that I'm on the right track for these sorts of
changes.

Currently, this assumes bundled elpa packages are checked out to
emacs/elpa, but it would not take much more work to also support
checking them out into emacs/lisp/... . That choice can be made on a
per-package basis; emacs/.gitmodules keeps track of where the bundled
packages are.

What works:

'make' generates PKGNAME-pkg.el, PKGNAME-autloads.el,  byte-compiles
packages.

'make clean' deletes the above.

Running the resulting emacs activates the bundled packages unless
package-load-list says not to.

'make-dist' adds the .el files from the bundled package to MANIFEST (ie,
to the distribution tarball).


What doesn't work yet:

'make' doesn't build bundled .info files

'make-dist' fails on making a directory link (on Windows/mingw64) - I
have not investigated this yet.

'make-dist' doesn't add .info, .elc from bundled packages.

I have not tried to build out of tree; this might just work, but
probably not.

-- 
-- Stephe