all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Joost Kremers <joostkremers@fastmail.fm>
Cc: 57503@debbugs.gnu.org
Subject: bug#57503: 28.1.91; package-selected-packages should not be saved to custom-file
Date: Fri, 02 Sep 2022 13:11:39 +0000	[thread overview]
Message-ID: <87h71pc450.fsf@posteo.net> (raw)
In-Reply-To: <87bks0368n.fsf@fastmail.fm> (Joost Kremers's message of "Wed, 31 Aug 2022 14:43:43 +0200")

Joost Kremers <joostkremers@fastmail.fm> writes:

> The variable `package-selected-packages` should not be saved to the users init
> file (or whatever `custom-file` points to). This was discussed before on
> emacs-devel but wasn't resolved:
>
> <https://lists.gnu.org/archive/html/emacs-devel/2016-02/msg00958.html> but 
>
> The gist of it is that if you keep your configuration under version control,
> having package-selected-packages written to your config file is inconvenient if
> you share your config across multiple machines but do not want to have the exact
> same set of packages installed on each.
>
> Even if you do want to keep the exact same set of packages on each machine, you
> still need to be careful about installing them, because the order of package
> installation affects the order of package-selected-packages, and so does
> deleting and reinstalling a package. As a result, I often experienced
> meaningless VC conflicts that needed to be resolved.
>
> IMHO the value of package-selected-packages should be written to a separate
> file, so that it's possible to put it under version control or ignore it,
> independently from the rest of one's configuration.

How about writing it into a file like "~/.config/emacs/elpa/selected-packages"?





  reply	other threads:[~2022-09-02 13:11 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 [this message]
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
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=87h71pc450.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=57503@debbugs.gnu.org \
    --cc=joostkremers@fastmail.fm \
    /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.