On Mon, 10 Jun 2024 at 19:47, Eli Zaretskii <
eliz@gnu.org> wrote:
> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> Date: Mon, 10 Jun 2024 18:51:08 +0200
> Cc: Philip Kaludercic <philipk@posteo.net>, acorallo@gnu.org, 71356@debbugs.gnu.org
>
> We don't want to change what :pin means, IMHO we need it to obey `package-install-upgrade-built-in`.
> That wouldn't be incompatible, right?
Right. But AFAIU, that was not what Philip was proposing. If I
misunderstood, my apologies.
So, in this, we are in "violent agreement" :-)
> So the sketch that actually loads org from elpa would be
>
> (let ((package-install-upgrade-built-in t))
> (use-package org
> :ensure t :pin gnu))
No, you are supposed to customize that option if you want built-in
packages to be upgraded as the rest of them. You aren't supposed to
let-bind user options.
Ahh, OK. I was just trying to sketch a test case. So the thing would be:
(custom-set-variables '(package-install-upgrade-built-in t))
(use-package org
:ensure t :pin gnu) ;; to upgrade from elpa
:init (message "org-version: %s" org-version))
(use-package eglot
:ensure t :: just to configure and initialise the built-in package
:init (message "init eglot"))
Is that what you mean?
-- Fragen sind nicht da, um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Headaches with a Juju log:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run a leader-deposed hook here, but we can't yet