Skip to content
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

bazel on darwin should mark output_base and output_user_root to not be backed up by Time Machine #1514

Closed
dmaclach opened this issue Jul 12, 2016 · 3 comments
Assignees

Comments

@dmaclach
Copy link
Contributor

currently output_base and output_user_root are by default going to be backed up by Time Machine, and this is not good. The fact that they are writing into var/tmp by default is saving most users right now (var/tmp is not backed up) but anybody who specifies their own options is going to get hit by this.

Please assign to me.

@kchodorow
Copy link
Contributor

Actually, @dslomov pointed out that if you're providing the directory, it's a bit weird to have Bazel change it's semantics for you.

@dmaclach
Copy link
Contributor Author

Xcode by default marks its output directories as not being backed up. All of this data can be regenerated so it doesn't make sense to be backing up gigs of build files IMHO

bazel-io pushed a commit that referenced this issue Jul 20, 2016
…ine on Darwin.

This is equivalent to what Xcode does with the directories that it generates as part its builds.

fix for #1514

--
MOS_MIGRATED_REVID=127927131
@ulfjack
Copy link
Contributor

ulfjack commented Dec 3, 2016

Looks like this was fixed. Closing.

@ulfjack ulfjack closed this as completed Dec 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants