-
Notifications
You must be signed in to change notification settings - Fork 43
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
Add support for offline compilation #38
Comments
Another solution would be only to compile when the source files have changed. This would allow the reuse of the cached binaries. |
@bevsxyz Thanks for creating the issue! I'm a bit uncertain about exactly what
But I'm uncertain about what that exactly does - why doesn't cargo In general I don't see that As seen above I don't really understand the current situation :), but perhaps we can move towards "offline by default when possible" - not only to work better without internet access, but also to reduce the overhead of running script (avoid slow network access when running a script) and reproducibility. |
@fornwall sorry about the delayed reply. I am not sure either of Perhaps this way of relying on time-stamp we may not have to call cargo every time and avoid that overhead. |
Here are some of the original offline mode issues/comments if that helps with clarification. The stabilization proposal give a pretty good tldr i think if it still holds true
|
@fornwall The commit where you added the It should only apply the offline flag if we don't have an internet connection. Tho i dunno how easy that would be or is there is a better method. Or if the offline flag even does what we want from this feature. |
@Blisto91 Thanks, reverted now! |
I wish to use rust-script with my i3blocks to obtain system temperature. My script works. But it required internet for compilation, and hence I could not run it during startup, and my bar ignored it completely. Can we make use of the cache and offer an
offline
compilation mode?cargo-script issue
Modes suggestion
The text was updated successfully, but these errors were encountered: