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

[Eli Zaretskii]

> From: address@hidden (Phillip Lord)
> Cc: address@hidden,  address@hidden
> Date: Tue, 18 Oct 2016 17:43:11 +0100
> 
> Org-mode v1 comes with a file called org-html. v1 is distributed with
> core emacs. Org-mode v2, however, no longer has a file called org-html,
> but does have a file called ox-html. Although org-mode v2 comes in the
> path before org-mode v1, it is still possible to load org-html.

That just means installing a new version needs to remove the previous
version's files first, that's all.  It has nothing to do with
load-path.

> Org-mode v1 comes with org-html. v1 is distributed through ELPA.
> Org-mode v2 comes with ox-html. We upgrade v1 to v2, and v1 is removed
> from the path. org-html is no longer loadable.

org-html doesn't need to be loadable if it doesn't exist in the new
version.  Again, nothing to do with load-path.

> My conclusion: having org-mode its own directory is a good thing. By
> extrapolation, therefore, having most or all packages in their own
> directory would be a good thing.

The extrapolation is invalid, because while Org is a very large
package, most other packages aren't.

> > If package.el already knows how to unload the old features and load
> > the new ones, it will continue doing this for any package, whether in
> > or out of core.  Right?
> 
> With the example that I have given, this fails at the moment for
> org-mode, specificially because org-mode is in core.

I don't understand why it fails, but if it's a missing feature in
package.el or in the infrastructure, we need to add that, in order to
move to having bundled packages on ELPA.