-
Notifications
You must be signed in to change notification settings - Fork 22
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
Easy installation via crates.io #51
Comments
sorry this project is in need of some house keeping, I will need to update at least 1 dependency before everything can work fine. I don't have time to do this for a few days, because of stuff I have going on in my personal life. Please be a little bit patient, I will work on it. |
No no worries, if there's any one thing I want to make clear it's that I don't expect you to bend over backwards or anything. I just really like this project and was interested in doing some hacking. The big thing I wanted to find out was if there was anything it would be preferred I look into first or something |
This tool is looks so cool! I also hope it can be published on crates.io, so one can simply run command like |
humm ok, on the map no eta tho, im kinda busy with life stuff |
try it to install sad: cargo install -f --git https://github.com/ms-jpq/sad --branch senpai it can work for me, perhaps it is useful for others. |
After futzing around for a little bit, I determined that the easiest way right now to install this package is to clone it, check out the latest release tag, and then run the
cargo install
command described in the readme. I actually ran through this twice because I also use ASDF and I wanted to use the same version of rust that you used to buildsad
so I could install from a clean repo before trying again with the version of rust I generally use as my toolchain in a global scope (1.49.0
).A couple of things I also wanted to check on before I just opened an issue on someone else's repo. I wanted to get a feel for how open to contributions you are and if there's anything that you'd rather someone take a look at first than publishing to crates.io. I generally try to open issues to see how open an author is to them (unless they're bugs) so that I can contribute.
The other option that can be floated if crates.io is an absolute no go is to update the README to include steps for checking out the latest tagged version
The text was updated successfully, but these errors were encountered: