Re: Adding use-package to core

[Philip Kaludercic <philipk@posteo.net>]

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> packages in a release (which should include the solution for how to
>> upgrade such packages after the released Emacs is installed on the
>> user's machine),
>
> FWIW, this has been a solved problem already in Emacs-24: package.el has
> always been able to handle the presence of both system-wide packages and
> user-installed packages and to pick the most recent version.

This is what has been confusing me about Eli's comments.  Debian does
this all the time, there are a great number of packages that can be
installed on a system-wide basis:

--8<---------------cut here---------------start------------->8---
$ apt search elpa-

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

Sorting...
Full Text Search...
elpa-a/testing 1.0.0-2 all
  functions for dealing with associative structures

elpa-ac-rtags/testing 2.38-6 all
  auto-complete back-end for RTags

elpa-ace-link/testing 0.5.0-3 all
  selecting a link to jump to

elpa-ace-popup-menu/testing 0.2.1-3 all
  replace GUI popup menu with something more efficient

elpa-ace-window/testing 0.10.0-1 all
  selecting a window to switch to
--8<---------------cut here---------------end--------------->8---

That is also why, in my eyes the issue is reduced to the matter of
deciding if the selected ELPA packages are bundled in Git (e.g. as
worktrees) or when the tarballs are generated (that distributions use to
build their packages).

But I am not done with reading through the archives, so I might just be
repeating stuff pointlessly.