-
-
Notifications
You must be signed in to change notification settings - Fork 679
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
add(nix): add crate2nix #1181
add(nix): add crate2nix #1181
Conversation
To have a better experience on ci, due to improved caching of dependencies. Also organize file hierarchy slightly.
Just a note: I have no idea which is better, just wanted to mention it. |
(The error I just mentioned actually looks a lot like the eval error this PR build just hit.) |
And same for me: ❯ nix build \
--eval-store auto \
--store 'ssh-ng://[email protected]' \
github:zellij-org/zellij/934939c0e68c35b0f82130d64ead3b02b4e82ee2
warning: error: SQLite database '/nix/var/nix/db/db.sqlite' is busy
error: a 'x86_64-linux' with features {} is required to build '/nix/store/jlhp550ybd3y8smlprsay0za4jz7psqm-addr2line-0.15.2.tar.gz.drv', but I am a 'aarch64-linux' with features {benchmark, big-parallel, gccarch-armv8-a, kvm, nixos-test} |
Thank you, this is really good input. I will definitely try out |
Thanks! Yeah, because of the IFD it still errors out, I seem to always forget that. |
Is needed because `nix flake check` accidentally tries to build IFD.
@colemickens, |
Looks ok: zjrev="407d251272e086a45110069233bab691cea48367"
❯ nix copy \
--eval-store auto \
--from 'ssh-ng://[email protected]' \
--to "ssh-ng://cole@$(tailscale ip --6 rpifour1)" \
--no-check-sigs \
"github:zellij-org/zellij/${zjrev}#packages.aarch64-linux.zellij-native"
❯ ssh cole@$(tailscale ip --6 rpifour1) \
nix run "github:zellij-org/zellij/${zj}#packages.aarch64-linux.zellij-native" \
-- --version
zellij 0.26.0 ignoring the version, looks like it works. (I thought I opened an issue for the version somewhere, maybe it was Matrix -- I assume zellij uses claps crate_version which takes version directly from the Cargo.toml... which can't really be re-written easily since you have to re-generate the lock. Options for fixing include maybe manually implementing |
Thank you for checking!
The version is correct, at least from our standpoint.
Yes, Ideally I would like to improve the version number |
I will merge this for now, |
To have a better experience on ci, due to improved caching
of dependencies. Also organize file hierarchy slightly.