nix: use rust-overlay for toolchain pinning
To ensure the Nix derivations are using the correct toolchain, defined
in the rust-toolchain file, use the rust-overlay library.
Also remove the fenix input, since this was actually never used and
was an artefact of some copy-paste shenanigans.
nix: add rad-web app
To allow for Nix users to install rad-web easily, add the package to
the set of packages and apps.
nix: use rust-overlay for toolchain pinning
To ensure the Nix derivations are using the correct toolchain, defined
in the rust-toolchain file, use the rust-overlay library.
Also remove the fenix input, since this was actually never used and
was an artefact of some copy-paste shenanigans.
nix: add rad-web app
To allow for Nix users to install rad-web easily, add the package to
the set of packages and apps.
Adding rad-web alone does not look useful. rad-web needs radicle-httpd to function and the radicle-httpd output already provides rad-web along with radicle-httpd.
It would be more important to provide a radicle-full output that includes both, radicle and radicle-httpd outputs.
Ya, that’s fair. I just realised I never added radicle-httpd to my NixOS setup and that’s why I was missing rad-web.
Do you have any pointers for how a flake can package multiple binaries under a single name? I’ve tried searching and messing around with it myself but not coming up with anything useful :(
I figured out I’d accidentally run nixos-rebuild boot instead of switch which was why it wasn’t working for me.
I’m not sure if there’s a helper for it or not, but you can make a derivation that just copies the results of the other two in installPhase.
e.g.
stdenv.mkDerivation {
pname = "radicle-client";
version = ...;
unpackPhase = "true";
installPhase = ''
mkdir -p $out/bin
cp ${radicle-cli}/bin/* $out/bin
cp ${radicle-httpd}/bin/* $out/bin
'';
}
Use buildEnv to merge radicle and radicle-httpd outputs
The canonical way to merge multiple packages into one is buildEnv.
Rebase.
Rebase.