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

[Eli Zaretskii]

> From: Achim Gratz <address@hidden>
> Date: Sat, 15 Oct 2016 19:08:35 +0200
> 
> No, it is not directly related to the directory structure.  But Emacs
> does collect all first-level autoloads for all elisp ("package" moniker
> or not) into a single file, with no provisions to deactivate them when a
> newer version of the same in-core package gets installed again.

This will have to be solved, of course.  We already have some
foo-autoloads.el files for some packages; perhaps that would be the
solution here as well.

> There are probably many different ways to tease this apart, but
> treating an in-core package no different than an out-of-core
> package, apart from the fact that it comes with the tarball and gets
> installed into a different tree has the advantage that it doesn't
> need completely new mechanisms to support it.

I don't think we will be able to treat these two classes of packages
the same.  I'm quite sure more and more reasons will pop up as we go.
So I believe we will have special treatment for ELPA packages anyway.
I just think that the directory in which they live as part of the
Emacs tree doesn't have to be part of that special treatment.