[core] Rework dotspacemacs-sync-packages behavior for site packages #16928
Conversation
bcc32
force-pushed
the
fix-site-package-lazy-install-behavior
branch
from
b5378af to
234761d
Compare
Even though packages with ":location site" cannot be installed from ELPA, they still need to be installed and present in package-alist in order to be configured correctly. This change fixes the following two bugs: 1. Used site packages that were present would be removed at startup, if `dotspacemacs-install-packages' was set to `used-only'. Of course, since the packages are typically installed at the system level, this would then noisily fail in `configuration-layer//package-delete'. After this commit, Spacemacs does not even consider these packages for deletion. 2. Used site packages that were missing failed to load in use-package but did not warn the user that the package failed to install in the first place. After this commit, Spacemacs more precisely informs the user that the package installation step went wrong, not load-path configuration.
This is noisy on startup and pretty pointless to warn users about. configuration-layer//package-delete will already skip such packages, but configuration-layer/delete-orphan-packages needs to be modified in order to avoid messaging about them still.
bcc32
force-pushed
the
fix-site-package-lazy-install-behavior
branch
from
234761d to
61add73
Compare
|
|
||
| ;; Do not noisily fail to delete system packages. | ||
| (setq orphans | ||
| (cl-delete-if (lambda (pkg-name) | ||
| (let ((pkg-desc (cadr (assq pkg-name package-alist)))) | ||
| (configuration-layer//system-package-p pkg-desc))) | ||
| orphans)) |
There was a problem hiding this comment.
Is this actually still necessary, after having declared site packages as distant? The PACKAGES passed to configuration-layer/delete-orphan-packages should never end up in the orphans list (the docstring seems misleading here). And IIUC the function should always get called with all distant packages.
There was a problem hiding this comment.
Ah, I finally understood that this is about unused site packages (which the commit message indeed says). An unused site package that is properly installed will end up in the orphans list when interactively calling configuration-layer/delete-orphan-packages. But then, if a user actually does this, perhaps they would like to be notified about such unused site packages?
With this change, the orphans-count still includes unused site packages. I guess this could look like a bug, so perhaps we should change this, or print some kind of message?
Perhaps we could consider one of the following alternatives:
- Move the
system-package-pcheck toconfiguration-layer//package-orphan-p? - Print a single message about the skipped site packages.
- Keep noisily trying to delete site packages (only in interactive calls, not on startup).
There was a problem hiding this comment.
My use case is for site packages that are installed by an administrator in a shared place, which the user should not be notified about because they cannot deleted by the user. I would at least like to be able to preserve this property, perhaps making it configurable. (3) seems appealing, but I'll need to think about it a little further.
There was a problem hiding this comment.
Makes sense. If you prefer, we can merge this first and then possibly improve it.
Fix #16898.
This PR consists of two commits that fix two separate bugs with site
packages. Please see the individual commit messages for details.