-
-
Notifications
You must be signed in to change notification settings - Fork 18.2k
emacsPackages: revert throw #457521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
wolfgangwalther
merged 1 commit into
NixOS:master
from
wolfgangwalther:ci-revert-emacs-packages-alias
Nov 1, 2025
Merged
emacsPackages: revert throw #457521
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we have to choose one, I slightly prefer removing
emacsPackagesfrom search.nixos.org over undeprecatingemacsPackagesas I said in #437197. But I am also fine with undeprecatingemacsPackages. WDYT? cc @adisbladis @AndersonTorres @panchohThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If
emacsPackagesgets removed from search.nixos.org, this means that users won’t be able to use search.nixos.org to locate Emacs packages at all, or that they will be exposed differently, maybe with an alternate prefix, or no prefix at all?(I would think that, as a user, being able to locate Emacs packages at search.nixos.org is desirable, to say the least).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I prefer removing it too.
The purpose of throw is precisely to break user config and force they to fix it, with the plus of being graceful.
But being graceful to user became being annoying to us packagers. Let's remove it and optionally make some announcement.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I very much agree.
Also, remember: Removing it essentially opts out of ever evaluating
emacsPackagesin CI. It's unlikely that these packages will be built by hydra, OK. Currently this also means they are not tested by GHA Eval. But my goal is to change that in the future. And for that to work, there needs to be something that can be recursed into -emacsPackages.Again, all other major package sets have this. There is no point in making emacs differ here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding
emacsPackagesto CI sounds good! MaybeemacsPackagescan be added to CI via something similarpackages-ocnfig.nix. (Just saying. I have not read the CI code and I do not think I have a say in CI things.)