-
Notifications
You must be signed in to change notification settings - Fork 77
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
Single-command install / depend on watchexec automatically #65
Comments
This is an exciting development. If there's any way I can help please let me know. |
This is now ready to release as soon as we watchexec's next release gets onto crates.io :) |
This is up on crates.io now as 1.8.1. One caveat: because |
No problem :) I'll tighten the version specifier, the advantage of this
method of embed is also that I *can* bind to versions tightly.
…On Thu, 27 Apr 2017, 02:26 Matt Green, ***@***.***> wrote:
This is up on crates.io now as 1.8.1.
One caveat: because watchexec is an app first and foremost, it will be
hard to continue to evolve and guarantee I won't break semver via changes
to to Args. Thus, in your shoes, I'd pin it to an exact version and bump
it only as necessary. (I'm not looking to break the Args struct anytime
soon, mind you.)
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#65 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAJgi7D7rXKsqxCDPbschgNtio_i-ukbks5rz1QEgaJpZM4NFQKN>
.
|
Done in 5.0.0. |
Note: you'll want to bump to watchexec 1.8.3 to avoid a dumb bug relating to file changes being triggered in |
Ah, that's not really an issue given I build my own Args — I'd already added .git ignoring — but ooops, I just noticed a bug/typo with that commit, so I'll fix that. (Also, you can avoid repetition by using |
To make v5 installable properly using the normal
cargo install cargo-watch
, we probably need to figure out how to either:The text was updated successfully, but these errors were encountered: