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
cargo-run-bin
#4204
Comments
I like this. We do have the required tools listed in flake.nix, but this would more user-friendly. The instructions for getting started would be:
|
Although, the flake.nix approach does have the benefit of having these binaries cached between projects (if they use the same version), so I wouldn't want to abandon that. The aliases you propose would break that. Could the aliases be set conditionally? |
Interesting point on There's dustinblackman/cargo-run-bin#7, but I think that just means that |
That issue is pointing to a PR that adds cargo-run-bin into nixpkgs, the main nix repository of software. There is no "works on nix", as nix is just a package manager that pull packages from repos. Our flake file is essentially just a list of stuff that we want installed, there is nothing more-involved. The main barrier is that one need nix installed, which is enough of a barrier to need other ways of listing dependencies. |
Totally, totally. I think the only outstanding question was whether using |
Yes, that is very probable. |
What's up?
https://github.com/dustinblackman/cargo-run-bin, from @dustinblackman
...looks cool — solves the problem of having to install lots of crates in
task setup-dev
.Instead, install this one, set some aliases, and it'll install the correct version of the binary whenever it's called if necessary.
The text was updated successfully, but these errors were encountered: