-
-
Notifications
You must be signed in to change notification settings - Fork 15.1k
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
attic-client: init at unstable-2024-02-08 #274481
Conversation
8b285de
to
4476185
Compare
Hi, thanks for the PR! I do wish that this is hold off before the first stable release where there could be some breaking changes. I've been putting this off for a while but hopefully I'll have more time this holiday season. |
Hi, thank you for the useful application! |
@zhaofengli are there news on this? |
In my opinion that is not a blocker, the package is marked as unstable so it's already explicit there will be breaking changes. |
If you agree I can update the package to the latest version and make it ready for reviews. |
I'd love to see this packaged, as I'd want to push stuff to our cache using GitHub Actions, but the current way of blindly pulling a specific derivation and using that doesn't feel right, at all. Even adding attic as a flake input (and trusting the "staging" Attic Instance as a substituter) results in us having to build attic-client ourselves. Given that it's explicitly marked as unstable, I also don't really see a reason to further delay packaging. On the contrary, it'd make using attic just so much easier. In case we really want to delay this further, I'll probably need to push this to my own cache and then fetch binaries from there... Not ideal, but the only alternative. |
Ok I updated it and chose that it's ok keeping all the binaries in the same derivation (feel free to criticize this choice). |
Apparently this lockFile = "${src}/Cargo.lock"; was causing an IFD to occur (probably the lockfile is parsed by nix at eval time?) and both lockFile = ./Cargo.lock; The nixpkgs manual suggests it (and I found many other packages doing the same). I also tried adding
|
@aciceri I think it would be good to package the tools separately. You can find the individual Cargo.toml files for the respective CLI tools in the folders, for example "client" for If you want, I can have a look at splitting up the packages, as well. But that'll probably take at least until the weekend. |
e49d857
to
55e9011
Compare
@Hayajiro I believe I haven't checked the most obvious place (upstream Also I updated @zhaofengli let me know if you want to be added between nixpkgs maintainers please.
|
Please add me to the maintainer list, thanks! |
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.
Changes LGTM so far. Will test the build output in a day or two (once I have the time to spare). That is, unless someone beats me to it.
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.
proud to say: just tested the client. works flawlessly
@ofborg build attic-client attic-server |
Hello!
https://gist.github.com/GrahamcOfBorg/71643bc5b784eb2a999dd94c7e2209fc Do you have an idea why? |
attic-server isn't being built by hydra for aarch64-linux for some reason: https://hydra.nixos.org/eval/1805789?filter=attic-server&compare=1805780&full= |
Description of changes
This adds a derivation for https://github.com/zhaofengli/attic that produces the following binaries:
attic
atticdm
atticd
Things done
Not tested yet (only
attic --version
).meta.mainProgram
is set toattic
(the client) since it's probably what most people expect to find buildingattic
.To be honest this is the first time I package something in Rust that produces multiple binaries and I don't know if it makes more sense keeping all the them in the same derivation or splitting it.
If there are systems where one of the binaries doesn't build/work it could make sense.
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.
@zhaofengli I hope you will appreciate this PR. Are you interested into being a nixpkgs maintainer for this?