Skip to content

pkgs/by-name: add version pins - #464396

Draft
quantenzitrone wants to merge 11 commits into
NixOS:masterfrom
quantenzitrone:by-name-version-pins
Draft

pkgs/by-name: add version pins#464396
quantenzitrone wants to merge 11 commits into
NixOS:masterfrom
quantenzitrone:by-name-version-pins

Conversation

@quantenzitrone

@quantenzitrone quantenzitrone commented Nov 23, 2025

Copy link
Copy Markdown
Contributor

Proof of concept implementation of NixOS/rfcs#192

Things done

  • Built on platform:
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • Tested, as applicable:
  • Ran nixpkgs-review on this PR. See nixpkgs-review usage.
  • Tested basic functionality of all binary files, usually in ./result/bin/.
  • Nixpkgs Release Notes
    • Package update: when the change is major or breaking.
  • NixOS Release Notes
    • Module addition: when adding a new NixOS module.
    • Module update: when the change is significant.
  • Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other READMEs.

Add a 👍 reaction to pull requests you find important.

@nixpkgs-ci nixpkgs-ci Bot added 2.status: merge conflict This PR has merge conflicts with the target branch 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux. 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. labels Nov 23, 2025
@qweered

qweered commented Jan 10, 2026

Copy link
Copy Markdown
Contributor

Conceptually looks good, what are next steps for this pr?

@quantenzitrone

Copy link
Copy Markdown
Contributor Author

probably get the rfc merged first, or do you think this is small enough to be done without the rfc?

@qweered

qweered commented Jan 10, 2026

Copy link
Copy Markdown
Contributor

we do need to hear opinion of @NixOS/nixpkgs-core at least

@qweered qweered mentioned this pull request Jan 11, 2026
13 tasks
@wolfgangwalther

Copy link
Copy Markdown
Contributor

we do need to hear opinion of @NixOS/nixpkgs-core at least

I'm not sure what the question to the core team here is. The core team generally is not a code owner that should be pinged for review. However, if local consensus can't be reached, we can surely help out.

In this case, the PR is a draft to support an ongoing RFC. The RFC is not done, yet. The PR fails CI. Nothing to do here.

@nixpkgs-ci nixpkgs-ci Bot added the 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md label Jul 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

2.status: merge conflict This PR has merge conflicts with the target branch 2.status: stale https://github.com/NixOS/nixpkgs/blob/master/.github/STALE-BOT.md 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 1-10 This PR causes between 1 and 10 packages to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants