-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
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
lianad: init at 6.0 #323696
lianad: init at 6.0 #323696
Conversation
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.
Thanks for opening this!
Left some comments, and it seems that only lianad
gets built without liana-cli
when withGui
is false
.
This comment was marked as resolved.
This comment was marked as resolved.
You are correct. I mischecked the result. |
bfb4fc3
to
93de3eb
Compare
26e0786
to
481b8c8
Compare
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.
Oops. Didn't see the PR title (I cannot edit it). Should be:
lianad: init at 5.0
lianad
+ liana-cli
executable options to liana
packageThere 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.
LGTM. 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.
it looks a bit weird because you are effectively making two derivation (which are different except for version and source.) into one. This may not be a good idea.
Good idea:
- Use callPackages to declare multiple packages.
- Just build them separately, and add a comment to remind keeping version the same
- Same to 2 but add assert to keep version the same. This may break r-ryantm, however
I agree in the current state it is not as discoverable / clear in the source what's going on, but I'm not sure which of those options more closely aligns to other packages that are in the same situation (see for example I'm unfortunately unaware of any documentation around this practice, but would love to keep consistent and still have this maintainable without breaking r-ryantm. Either way, if this should be a separate package declaration, I'll help if we need to keep them in sync manually without an |
That's Yes, there are more cursed examples, see |
Right, got it. Thanks @Aleksanaa for clearing that up! So let's not add to the cursed list then :) I'm inclined to go with Option 2 and have a separate package declaration in We can investigate option 3 at some later stage. |
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.
Just changing the approval status to make it clear we're splitting this package.
pkgs/by-name/li/lianad/package.nix
Outdated
hash = "sha256-RkZ2HSN7IjwN3tD0UhpMeQeqkb+Y79kSWnjJZ5KPbQk="; | ||
}; | ||
|
||
cargoSha256 = "sha256-6r8G4sO/aDO5VyJbmbdFz3W2b8ZmulXJZtnz8IAwcaU="; |
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.
cargoSha256 = "sha256-6r8G4sO/aDO5VyJbmbdFz3W2b8ZmulXJZtnz8IAwcaU="; | |
cargoHash = "sha256-6r8G4sO/aDO5VyJbmbdFz3W2b8ZmulXJZtnz8IAwcaU="; |
pkgs/by-name/li/lianad/package.nix
Outdated
|
||
meta = with lib; { | ||
mainProgram = "lianad"; | ||
description = "A Bitcoin wallet leveraging on-chain timelocks for safety and recovery"; |
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.
description = "A Bitcoin wallet leveraging on-chain timelocks for safety and recovery"; | |
description = "Bitcoin wallet leveraging on-chain timelocks for safety and recovery"; |
pkgs/by-name/li/lianad/Cargo.lock
Outdated
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.
Please delete this
0229986
to
ef5ddcd
Compare
Need to run |
ef5ddcd
to
af7dbcc
Compare
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.
Needs rebase and should init at 6.0 now. I had to update liana
as 5.0 had build errors with rust 1.80: #333059
6916e8d
to
a60f686
Compare
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.
Thanks! Last few comments 🤞
f496993
to
bc8b4e3
Compare
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.
First commit message should be `lianad: init at 5.0`
bc8b4e3
to
5067b8b
Compare
Description of changes
the
liana
package currently only supports theliana-gui
executable, while it is desired to also support headless use-casesthis PR adds a
withGui
attribute, which is used to choose between:liana-gui
executable ifwithGui
istrue
lianad
+liana-cli
executables ifwithGui
isfalse
(plus a$out/etc/liana/config.toml
based onlianad_config_example.toml
)cc @dunxen
Things done
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.