-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
mtime-on-use as a config option #6978
Labels
Z-mtime-on-use
Nightly: mtime-on-use
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#6477 told Cargo to touch files that it reads even when Cargo does not use the
mtime
of that file. This is needed for outside tools (like cargo-sweep) to clean up the target directory. Unfortunately this broke the playground. So it was put behind themtime-on-use
feature flag in #6573. It would be easier to test as a set and forget config option which would come with a env var automatically. This setup, an unstable config option for testing a new internal detail, was used for #6883, and it worked well. So at the last Cargo meeting the Team decided it was ok to switch themtime-on-use
feature flag to atest-track-file-usage
config option. This option would be well documented as unstable and still in development. It would also be ignored if Cargo is being run on the stable channel.Help making this happen would be lovely.
The text was updated successfully, but these errors were encountered: