From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71356@debbugs.gnu.org, Philip Kaludercic <philipk@posteo.net>,
acorallo@gnu.org
Subject: bug#71356: use-package doesn't load org from elpa
Date: Mon, 10 Jun 2024 18:51:08 +0200 [thread overview]
Message-ID: <CAO48Bk8wTW+5KpNZrVt-dnCEfDCBFCukD9ACLpV9a88Dw-mRXw@mail.gmail.com> (raw)
In-Reply-To: <86cyoo93pw.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1636 bytes --]
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?
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))
whereas
(use-package org
:ensure t :pin gnu)
would keep the original org packaged with emacs (called with emacs -Q)
Best, /PA
On Mon, 10 Jun 2024 at 18:12, Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Philip Kaludercic <philipk@posteo.net>
> > Cc: Andrea Corallo <acorallo@gnu.org>, paaguti@gmail.com,
> > 71356@debbugs.gnu.org
> > Date: Mon, 10 Jun 2024 15:40:58 +0000
> >
> > >> > To me :pin would make perfect sense, as it explicitly expresses what
> > >> > archive we want to follow for package upgrades.
> > >>
> > >> +1, also use-package interface is very declarative and I'm not sure
> > >> having it influenced by a dynamic var would match user expected
> > >> behavior.
> > >
> > > If you prefer, we could add a new :foo keyword to mean this. But
> > > unconditionally changing what :pin means in these cases is out of the
> > > question.
> >
> > We wouldn't change what :pin means directly, but just have
> > package-install respect `package-pinned-packages'.
>
> How is that different? It's an incompatible change of behavior, and I
> cannot agree to that, sorry.
>
--
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
[-- Attachment #2: Type: text/html, Size: 2814 bytes --]
next prev parent reply other threads:[~2024-06-10 16:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-04 6:26 bug#71356: use-package doesn't load org from elpa Pedro Andres Aranda Gutierrez
2024-06-04 21:44 ` Andrea Corallo
2024-06-05 6:40 ` Pedro Andres Aranda Gutierrez
2024-06-05 11:18 ` Eli Zaretskii
2024-06-05 18:09 ` Andrea Corallo
2024-06-06 5:46 ` Pedro Andres Aranda Gutierrez
2024-06-06 6:02 ` Eli Zaretskii
2024-06-06 6:11 ` Pedro Andres Aranda Gutierrez
2024-06-06 9:15 ` Eli Zaretskii
2024-06-06 6:15 ` Philip Kaludercic
2024-06-06 9:21 ` Eli Zaretskii
2024-06-06 15:07 ` Pedro Andres Aranda Gutierrez
2024-06-06 15:19 ` Eli Zaretskii
2024-06-07 8:05 ` Pedro Andres Aranda Gutierrez
2024-06-10 6:02 ` Philip Kaludercic
2024-06-10 6:52 ` Pedro Andres Aranda Gutierrez
2024-06-10 8:17 ` Andrea Corallo
2024-06-10 12:18 ` Eli Zaretskii
2024-06-10 15:40 ` Philip Kaludercic
2024-06-10 16:12 ` Eli Zaretskii
2024-06-10 16:51 ` Pedro Andres Aranda Gutierrez [this message]
2024-06-10 17:46 ` Eli Zaretskii
2024-06-10 18:04 ` Philip Kaludercic
2024-06-11 5:27 ` Pedro Andres Aranda Gutierrez
2024-06-11 7:29 ` Eli Zaretskii
2024-06-11 7:53 ` Pedro Andres Aranda Gutierrez
2024-06-10 12:14 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAO48Bk8wTW+5KpNZrVt-dnCEfDCBFCukD9ACLpV9a88Dw-mRXw@mail.gmail.com \
--to=paaguti@gmail.com \
--cc=71356@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=philipk@posteo.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).