-
Notifications
You must be signed in to change notification settings - Fork 296
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
flake.nix
(or; remove need for --impure
flag on nixos install)
#3029
Comments
Hi @quinn-dougherty we only give official support by using the signed installers from www.daedaluswallet.io But I am sure @michalrus could give you an answer here 🙏 |
Hey, @quinn-dougherty! If you want flakes, you can try this in-progress PR → #3008 We use some impure evaluations for code signing of the Windows builds, so it may take some time, before this is merged into If #3008 works for you, I can merge the current |
Or you can also look at that diff, to see what I had to change to make it build purely. Unfortunately, IIRC, I don’t think that passing |
flake.nix
flake.nix
(or; remove need for --impure
flag)
flake.nix
(or; remove need for --impure
flag) flake.nix
(or; remove need for --impure
flag on nixos install)
So
works great, and the reason I can't build my system is the package isn't interacting with fish completions
Which isn't super important to you, but I figured it couldn't hurt to make you aware. Thanks for the branch! |
Oh, so there is no Interesting 😮 Thanks! 🙇 I’ll add it 📝 |
FWIW this seems to work fine for me on Linux on the 5.1.1 tag {
inputs.daedalus.url = "github:input-output-hk/daedalus/5.1.1";
outputs = { nixpkgs, daedalus, ... }: {
# ...
home.packages = [
(import daedalus {
target = "x86_64-linux";
localLibSystem = "x86_64-linux";
}).daedalus
];
# ...
};
} |
I'm running nixos, and I can't install daedalus in pure mode. I need to run
--impure
flag onnixos-rebuild switch
, or else I get the following bugMy install looks like this, with
home-manager
:I think a flake would be a better way to install daedalus.
The text was updated successfully, but these errors were encountered: