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

[Eli Zaretskii]

> From: address@hidden (Phillip Lord)
> Cc: Eli Zaretskii <address@hidden>,  <address@hidden>,  <address@hidden>
> Date: Wed, 19 Oct 2016 21:24:03 +0100
> 
> > - emacs -Q
> >
> > - Eval the following fragment, after having replaced [path-to] to the
> >   proper path where the example was extracted to:
> >
> >   (push "[path-to]/deprecated-feature-example/foo-package-1.0" load-path)
> >   (push "[path-to]/deprecated-feature-example/foo-package-2.0" load-path)
> >   (require 'foo-old)
> >   => an error will be signaled "foo-old is no longer supported..."
> >
> > But don't get me wrong.  I really don't think this will be the usual
> > case.  In most if not all packages, accounting for such misuses won't be
> > required at all.  I just wanted to prove it's not an unsolvable problem.
> 
> I like this, and it gives a nice error message of deprecation, and I
> think that is good. But this is a solution which requires package
> developers to explicitly support declarations of deprecation.

If this is what we want, I see no reason to require such support in
the packages that will be bundled.  They are Emacs core packages for
all purposes, so we are requiring this from ourselves.