From: Corwin Brust <corwin@bru.st>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 53885@debbugs.gnu.org
Subject: bug#53885: 28.0.51 [PATCH] Autoload package-installed-p
Date: Wed, 9 Feb 2022 17:58:25 -0600 [thread overview]
Message-ID: <CAJf-WoT6yiXN1yQf3_w_Yr5fu7Ri0wHePAfco3iFZCx_9OAe2w@mail.gmail.com> (raw)
In-Reply-To: <87v8xng5ig.fsf@gnus.org>
On Wed, Feb 9, 2022 at 2:16 PM Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> It should be safe for the release branch, so installing it is fine by
> me, but I didn't really understand the use case.
Sorry I failed in making the case for users clear.
The primary use-case here is "repeatable configuration", especially
bootstrapping `use-package'.
By "repeatable configuration" we mean, we get the same setup each time
we start Emacs, even when launching for the first time on a new host.
The use package feature provides an "ensure" capability that is well
suited to this job.
(use-package 'foo :ensure t)
This appears widely used, especially to create literate Emacs configurations.
For this to work, however, "bootstrapping" (installing use-package via
Emacs core features) is needed. The reproducer I gave shows one way
of bootstrapping use-package. Considering the similarity of my
reproducer to the recipe in #31397, I think it is a fairly common
approach and has been for some years.
next prev parent reply other threads:[~2022-02-09 23:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 23:55 bug#53885: Autoload package-installed-p Corwin Brust
2022-02-09 0:05 ` bug#53885: 28.0.51 [PATCH] " Corwin Brust
2022-02-09 13:37 ` Eli Zaretskii
2022-02-09 20:16 ` Lars Ingebrigtsen
2022-02-09 23:58 ` Corwin Brust [this message]
2022-02-10 6:10 ` Eli Zaretskii
2022-02-10 6:45 ` Lars Ingebrigtsen
2022-02-10 7:21 ` Corwin Brust
2022-02-10 7:57 ` Eli Zaretskii
2022-02-10 8:09 ` Corwin Brust
2022-02-10 8:18 ` Eli Zaretskii
2022-02-10 8:41 ` Lars Ingebrigtsen
2022-02-10 8:49 ` Corwin Brust
2022-02-10 12:04 ` Eli Zaretskii
2022-02-10 14:54 ` Corwin Brust
2022-02-10 17:29 ` Eli Zaretskii
2022-02-09 5:39 ` bug#53885: " Corwin Brust
2022-02-09 14:39 ` Augusto Stoffel
2022-02-09 15:39 ` Corwin Brust
2022-02-10 8:42 ` Augusto Stoffel
2022-02-10 8:59 ` Philip Kaludercic
2022-02-10 9:28 ` Augusto Stoffel
2022-02-10 9:23 ` Corwin Brust
2022-02-10 9:30 ` Augusto Stoffel
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=CAJf-WoT6yiXN1yQf3_w_Yr5fu7Ri0wHePAfco3iFZCx_9OAe2w@mail.gmail.com \
--to=corwin@bru.st \
--cc=53885@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).