-
-
Notifications
You must be signed in to change notification settings - Fork 14k
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
Automate rustRegistry updates #14469
Comments
Given that snapshot update can't break anything in theory (we require |
Crates.io never had an unpublish feature, they only remove things for legal reasons: https://www.reddit.com/r/rust/comments/4bm3rk/how_would_cratesio_react_in_a_case_similar_to_the/d1bqxc0 You're right about directly pushing to master; after a while, nobody's going to check generated commits anyway and will just hit merge. In the unlikely case something breaks, we can always revert it. |
This sounds good to me. I really like the way the rust infrastructure works in Nix relative to the other languages where you have to use Nix file generators, depsSha256 and then making Cargo deterministic is clever. Specifically for how the script updates the crates index, perhaps this new Nix feature might be of some use: NixOS/nix@06f29fa Here's some other things it could update (not necessarily in first implementation, but eventually):
|
I think that this can be fixed with https://github.com/alexcrichton/cargo-local-registry This would allow creating a local registry with only the package specified in a Cargo.toml file. This should be constant over time (and is verfiied by hashes) and would eliminate the need to have the registry package at all. I might try to get it working but I'm not faimilar with the rust packaging and the tool itself has a number of dependencies which I would probably need to build manually to avoid a circular dependency. |
Thank you for your contributions. This has been automatically marked as stale because it has had no activity for 180 days. If this is still important to you, we ask that you leave a comment below. Your comment can be as simple as "still important to me". This lets people see that at least one person still cares about this. Someone will have to do this at most twice a year if there is no other activity. Here are suggestions that might help resolve this more quickly:
|
we don't have a rustRegistry anymore |
Having to update rustRegistry manually is super annoying when you're developing in Rust.
I propose adding a script to nixpkgs that can generate the latest version, and then put a
.travis.yml
in a repo that calls the script and submits a PR, invoked daily by Nightli.es. Alternatively, it could be a cronjob running on nixos.org infrastructure. This would also be reusable for other packages.cc @abbradar @trishume @jagajaga What do you think?
The text was updated successfully, but these errors were encountered: