-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
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
tarball: backport nixos-search's subsets for JSON generation #105857
tarball: backport nixos-search's subsets for JSON generation #105857
Conversation
NixOS-search uses a list with outdated packages sets because it needs to stay compatible with stable branches
/marvin opt-in |
Hi! I'm an experimental bot. My goal is to guide this PR through its stages, hopefully ending with a merge. You can read up on the usage here. |
Is this going to influence the speed of the bash-completion script when doing nix-build -A Tab? |
@SuperSandro2000 The evaluation cache in Nix master speeds up tab completion, e.g. |
I don't think this would affect bash completion for AFAICT, this file is only used in the build script of
|
/status needs_reviewer |
A few questions:
|
I don't think it was generated. It looks like it was picked out manually. If we add another larger subset of packages, we should just manually update the list. That's a rare enough of an occurance to not cause too much trouble I think.
For Repology, it doesn't matter. They take care of duplicates etc. I don't know whether there are other users but I'm pretty sure there aren't. I the only thing I can think of that could possibly be using it is If there are users who can't deal with duplicates we could either just export the latest versions or export the longer list as a separate JSON (maybe even the nearly complete list).
Yeah that's what I was thinking too. Although, the set of packages not in both sets probably isn't too large in most cases. |
/status needs_merger |
I'm a bit -0 on this one, since it does not addresses the real problem. Somebody will have to keep this list manually up to date. It would be nicer if this list would not be even needed. But I understand that this solved the problem currently, therefore I'm not against it, but would like to challenge that the problem to be addressed at the root. |
Reminder: Please review! Reminder: This Pull Request is awaiting merger. If you are the assigned reviewer with commit permission, please have a look. If you can't, please say so. If the status is not accurate, please change it. If nothing happens, this PR will be put back in the |
Since this discussion has stalled a bit and it seems like nobody is working on a better solution, I think something is better than nothing for now. So I'm calling "FCP with predisposition to merge" now. Unless somebody disagrees, I'll merge on Wednesday. |
The only thing I was worried about being affected would be |
Reminder: Please review! Reminder: This Pull Request is awaiting merger. If you are the assigned reviewer with commit permission, please have a look. If you can't, please say so. If the status is not accurate, please change it. If nothing happens, this PR will be put back in the |
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.
Thank you for working on this @Atemu!
Issue on fixing this properly: #107539 |
This pull request has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/nixpkgs-has-been-the-largest-repository-for-months/10667/1 |
Motivation for this change
Progress towards #102508
More limited scope than #102509
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)