Re: decision on moving core packages to ELPA; also move to obsolete?

[Stefan Monnier]

>> every ELPA package we want to include will have
>> a branch in `emacs.git` (e.g. with name `elpa/[PKGNAME]`)
> It's the other way around: each package in elpa.git will have branch
> named emacs/PKGNAME.  Right?

If we want to use them in all Git checkouts, then I assumed it'd make
sense to host them in `emacs.git`.  But either way is fine by me.

>> We will place the submodules under some `elpa` subdirectory of our
>> choice
> Why not under lisp/ ?

Because we don't want it to interfere with the subdirs.el and other
such things.

> And what directory will be the parent of that elpa/ subdirectory you
> propose, when Emacs is installed?

I think it'd makes sense to put use /usr/share/emacs/NN.MM/elpa
(i.e. keep it as a sibling of `lisp` both in the source code and in the
install).

>> after which we simply have to add that directory to the default
>> value of `package-directory-list`.
> Note that this is not a single directory, but at least 2 different
> ones: we need to support both running Emacs uninstalled, from the
> source/build tree, and running an installed Emacs.

It's only one directory, but indeed just like `etc`, `lisp`, and others,
its location will depend on whether Emacs is run uninstalled or not.


        Stefan