Re: decision on moving core packages to ELPA; also move to obsolete?

[Stephen Leake]

Stephen Leake <stephen_leake@stephe-leake.org> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Stefan Monnier <monnier@iro.umontreal.ca>
>>> Cc: Daniele Nicolodi <daniele@grinta.net>,  stephen_leake@stephe-leake.org,
>>>   emacs-devel@gnu.org
>>> Date: Tue, 15 Dec 2020 12:03:57 -0500
>>> 
>>> >> Org is distributed as part of Emacs but it is routinely also
>>> >> installed and updated from ELPA and AFAIK it does not implement any
>>> >> special trick to make this work smotly.
>>> > The idea is that users should be able to install, upgrade, and
>>> > downgrade such packages exactly like they do with unbundled ones.
>>> 
>>> I still don't see what's the problem.
>>> 
>>> With current Emacs, users can upgrade/downgrade their version of Org,
>>> python.el (etc...) via `list-packages`.  Clearly the same would apply to
>>> bundled ELPA packages.
>>
>> Doesn't package.el install stuff under ~/.emacs.d/elpa/ ?
>
> yes.
>
>> > If so, what happens with installed Lisp files under /usr/share/ ?
>
> They stay there, but ~/.emacs.d/elpa is earlier in load-path.

And also, once bundling ELPA packages in the tarball works, the package
can be removed from Emacs core, simplifying the pakcage maintenance
process.

-- 
-- Stephe