-
Notifications
You must be signed in to change notification settings - Fork 377
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
Allow writing Cargo.toml
in project directory.
#348
Conversation
181419d
to
6f8b258
Compare
6f8b258
to
83778cb
Compare
bors try |
tryBuild succeeded
|
Would it be possible to instead mount the Cargo.toml file in docker as rw as an alternative? |
No, since it's a file. You can only mount directories as a volume. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a big fan of this change, it's a bit of a capitulation.
But if you think it's the only way I'll approve it.
I mean there could be another way, but I'm pretty sure it wouldn't be worth the additional complexity for virtually no gain. If this really was a big enough problem, |
I'm pretty certain it's possible in docker. |
You're right, seems like it is indeed possible. Still, this wouldn't work in the case when |
bors r+ |
348: Allow writing `Cargo.toml` in project directory. r=therealprof a=reitermarkus The project directory was previously deliberately mounted as read-only since “well behaved crates should only ever write to `$OUT_DIR` and never modify `$CARGO_MANIFEST_DIR`”. That however, breaks the `--locked` flag and is not worth the additional complexity. Fixes #346. Co-authored-by: Markus Reiter <me@reitermark.us>
Build succeeded |
The project directory was previously deliberately mounted as read-only since “well behaved crates should only ever write to
$OUT_DIR
and never modify$CARGO_MANIFEST_DIR
”. That however, breaks the--locked
flag and is not worth the additional complexity.Fixes #346.