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

[Eli Zaretskii]

> From: Alain Schneble <address@hidden>
> Date: Wed, 19 Oct 2016 22:13:09 +0200
> Cc: address@hidden
> 
> >                                                                   That
> > precludes almost all solutions that depend on removal or shadowing
> > during later steps in the initialization sequence and where
> > not-yet-to-be-initialized packages become visible when initializing
> > another package.
> 
> I can only think of some inconsistent inter-package dependencies here.
> But this will be covered by the "requires min package version"
> dependency management that is already in place in package.el AFAIK.

Yes, updating a package should also update all of its dependencies.
And it should bail out if some of the dependencies are not yet
available (e.g., if some dependency package was not yet update to
account for the changes in the main package).