From: <jakanakaevangeli@chiru.no>
To: Lars Ingebrigtsen <larsi@gnus.org>, Robert Pluim <rpluim@gmail.com>
Cc: Joost Kremers <joostkremers@fastmail.fm>,
57503@debbugs.gnu.org, Philip Kaludercic <philipk@posteo.net>,
Stefan Kangas <stefankangas@gmail.com>
Subject: bug#57503: 28.1.91; package-selected-packages should not be saved to custom-file
Date: Tue, 06 Sep 2022 18:45:21 +0200 [thread overview]
Message-ID: <87czc8pi3i.fsf@miha-pc> (raw)
In-Reply-To: <87ilm0vlk7.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Robert Pluim <rpluim@gmail.com> writes:
>
>> How do we define 'fresher'?
>
> I left that as an exercise for the reader. 🫠
>
>> Anyway, if in doubt, use brute force:
>>
>> (define-multisession-variable package-selected-packages-ms
>> (package--find-non-dependencies))
>>
>> works fine. We could even condition it on `package-selected-packages'
>> being non-nil.
>
> Hm... I wonder whether we could just drop the variable altogether.
> That is, checking for freshness sounds like as much work as
> recalculating the variable.
>
> What are the actual effects of the variable? That is, what code is it
> supposed to speed up?
Isn't it used for distinguishing packages installed automatically as
dependencies from packages installed explicitly by the user? This
affects M-x package-autoremove.
And if my opinion counts, I like having the variable in my .emacs,
possibly under revision control. On a fresh machine, I can then simply
type M-x package-install-selected-packages to install all the packages
from the variable, and M-x package-autoremove to uninstall all packeges
not in listed the variable.
next prev parent reply other threads:[~2022-09-06 16:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 12:43 bug#57503: 28.1.91; package-selected-packages should not be saved to custom-file Joost Kremers
2022-09-02 13:11 ` Philip Kaludercic
2022-09-02 13:17 ` Robert Pluim
2022-09-02 13:17 ` Lars Ingebrigtsen
2022-09-02 14:33 ` Robert Pluim
2022-09-03 9:52 ` Lars Ingebrigtsen
2022-09-03 10:17 ` Philip Kaludercic
2022-09-03 12:25 ` Lars Ingebrigtsen
2022-09-03 15:32 ` Stefan Kangas
2022-09-04 10:52 ` Lars Ingebrigtsen
2022-09-05 7:37 ` Robert Pluim
2022-09-05 11:16 ` Lars Ingebrigtsen
2022-09-05 11:51 ` Robert Pluim
2022-09-05 13:14 ` Robert Pluim
2022-09-05 19:04 ` Lars Ingebrigtsen
2022-09-06 8:18 ` Robert Pluim
2022-09-06 10:34 ` Lars Ingebrigtsen
2022-09-06 13:49 ` Robert Pluim
2022-09-06 14:30 ` Robert Pluim
2022-09-06 16:45 ` jakanakaevangeli [this message]
2022-09-07 0:09 ` Stefan Kangas
2022-09-07 5:38 ` jakanakaevangeli
2022-09-07 9:55 ` Robert Pluim
2022-09-07 12:39 ` Lars Ingebrigtsen
2022-09-03 15:33 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czc8pi3i.fsf@miha-pc \
--to=jakanakaevangeli@chiru.no \
--cc=57503@debbugs.gnu.org \
--cc=joostkremers@fastmail.fm \
--cc=larsi@gnus.org \
--cc=philipk@posteo.net \
--cc=rpluim@gmail.com \
--cc=stefankangas@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.