-
Notifications
You must be signed in to change notification settings - Fork 84
feat(nix flake): Update floresta build that supports bitcoin kernel and re export packages #741
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
feat(nix flake): Update floresta build that supports bitcoin kernel and re export packages #741
Conversation
2d82994 to
d2d1da0
Compare
1d9fe1e to
bdd211b
Compare
|
rebased with master @Davidson-Souza |
|
can you gimme a review ma fellow nix user @j-moreno-c-r |
|
LGTM, but Python functional tests will not work if the binary declaration is "bitcoin" instead of "bitcoind"... as already mentioned in the PR. #742, all the rest looks fine... |
You should obtain bitcoin from the script and not by nix anymore. Now python is a dependency for the whole floresta project to compile, im thinking to just include uv in the default shell and be satisfied by it, WYT ? |
Okay, this should work fine. I don't think including uv in the default shell is a problem,this makes it simpler |
bdd211b to
fa8e24c
Compare
|
May i have some review here ? @j-moreno-c-r @moisesPompilio |
|
Did these modifications make this commit 598db3e from that PR obsolete? Will your PR already resolve this flaky nix part? |
fa8e24c to
cb4983e
Compare
cb4983e to
52c850b
Compare
|
52c850b updated with @moisesPompilio suggestions |
|
code review ACK 52c850b I don't use Nix, but the proposed changes are ok. |
what, I thought you did 😆. |
|
Wait i can update the link to getfloresta now |
|
tACK 52c850b on Nixos 25.11 |
52c850b to
199abcf
Compare
Yes, I updated the stable nixpkgs version... run a nix flake update and should be fine. I also updated the url to the |
|
code review ACK 199abcf |
|
tACK 199abcf |
199abcf to
68a0a79
Compare
|
Done in 68a0a79 |
Davidson-Souza
left a comment
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.
crACK 68a0a79. I don't have nix installed to test the changes, though.
|
tACK 68a0a79 |
68a0a79 to
84ac5f9
Compare
…el and re export packages.
|
Okay, i revised the whole docs page and explicitely added |
I didn't see any of those changes here, wdym? |
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.
utACK 84ac5f9
Davidson-Souza
left a comment
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.
re-ACK 84ac5f9
|
crACK 84ac5f9 |
84ac5f9 to
652a5d4
Compare
Forgot to push it lol Sry yall |
JoseSK999
left a comment
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.
re-ACK 652a5d4
Davidson-Souza
left a comment
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.
re-ACK 652a5d4
|
tACK 652a5d4 |
|
crACK 652a5d4 |
Description and Notes
we had some previous changes moving the build expressions outside this repo.
I kept it simple so we could work without worries about packaging dealing but what i did was about to be broken by bitcoin kernel.
This Pr consumes the build expression from floresta-flake which now supports bitcoin kernel.
Depends on #456
How to verify the changes you have done?
This branch builds on top of the #456, check out on it to ensure that it contain the changes that introduced the bitcoin kernel
nix flake check --all-systems # Will do static evaluation on the flake.
nix build # will build the default package, which is the same as just
cargo buildon the workspace.Contributor Checklist
just pcc(recommended but slower)just lint-features '-- -D warnings' && cargo test --releaseFinally, you are encouraged to sign all your commits (it proves authorship and guards against tampering—see How (and why) to sign Git commits and GitHub's guide to signing commits).