From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 71356@debbugs.gnu.org, acorallo@gnu.org,
Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
Subject: bug#71356: use-package doesn't load org from elpa
Date: Mon, 10 Jun 2024 18:04:14 +0000 [thread overview]
Message-ID: <8734pkznc1.fsf@posteo.net> (raw)
In-Reply-To: <865xug8zcf.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 10 Jun 2024 20:46:56 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> 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.
No it wasn't. I was proposing to add `package-pinned-packages' as an
alternative to `package-install-upgrade-built-in' to upgrade specific
packages.
>> 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.
--
Philip Kaludercic on peregrine
next prev parent reply other threads:[~2024-06-10 18:04 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
2024-06-10 17:46 ` Eli Zaretskii
2024-06-10 18:04 ` Philip Kaludercic [this message]
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=8734pkznc1.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=71356@debbugs.gnu.org \
--cc=acorallo@gnu.org \
--cc=eliz@gnu.org \
--cc=paaguti@gmail.com \
/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).