Re: feature/integrated-elpa 4f6df43 15/23: README added

[Eli Zaretskii]

> From: address@hidden (Phillip Lord)
> Cc: address@hidden,  address@hidden,  address@hidden
> Date: Tue, 18 Oct 2016 17:59:28 +0100
> 
> >>  - Enable a built emacs to build and test all packages in ELPA whether
> >>    they are core/tarball or not.
> >
> > Can this be done while keeping the current structure under lisp/
> > intact and putting packages from ELPA under lisp/ ?  If yes, I think
> > this is what we all want.
> 
> 
> I can easily do:
> 
> 
> EMACS/lisp
> EMACS/lisp/lots-of-files.el
> EMACS/lisp/textmodes/
> EMACS/lisp/progmodes
> EMACS/lisp/packages
> EMACS/lisp/packages/package-1
> EMACS/lisp/packages/package-2
> EMACS/lisp/packages/package-3

As already discussed, this is not what we want.

> I could less easily do:
> 
> EMACS/lisp
> EMACS/lisp/lots-of-files.el
> EMACS/lisp/textmodes/package-1
> EMACS/lisp/progmodes/package-2
> EMACS/lisp/emacs-lisp/package-3

This is what we want.  IOW, we want foo.el to live in the same
directory it is now, even if its Git repository will be on ELPA.

> This requires updating the current build process to exclude multiple
> directories

Why do we need to exclude directories during the build?  And what does
"exclude" mean in this context?

> I also dislike this, because I think it mixes up files of different
> kinds in the tree (that is files which are in place in the Emacs git
> repo, and those which are not).

There are no different kinds.  They are all of the same kind: Lisp
packages that are bundled with a release tarball.  The fact that some
of them are in a separate Git repo  doesn't make them a different
kind.  We want the move to ELPA to be transparent as far as the Emacs
lisp/ directory structure is concerned.

> Finally, it would no doubt be possible to do:
> 
> EMACS/lisp
> EMACS/lisp/textmodes/package-1a.el
> EMACS/lisp/textmodes/package-1b.el
> EMACS/lisp/textmodes/package-1c.el
> EMACS/lisp/progmodes/package-2.el
> EMACS/lisp/emacs-lisp/package-3.el

Where 1a, 1b, and 1c are different versions of the same package?  This
is not required; the updates of bundled packages should go into
~/.emacs.d/elpa/, I think.