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

gitignore: ignore target as a symlink #133

Merged
merged 1 commit into from
Oct 4, 2019

Conversation

mathstuf
Copy link
Contributor

@mathstuf mathstuf commented Oct 1, 2019

No description provided.

@bluss
Copy link
Owner

bluss commented Oct 4, 2019

Curious where this use case comes from

@bluss bluss merged commit 8c3634a into bluss:master Oct 4, 2019
@tbu-
Copy link
Collaborator

tbu- commented Oct 4, 2019

If you want to move all cargo target dirs globally, just do

export CARGO_TARGET_DIR=/var/tmp/cargo

@mathstuf mathstuf deleted the target-as-symlink branch October 4, 2019 19:33
@mathstuf
Copy link
Contributor Author

mathstuf commented Oct 4, 2019

I keep my build trees on a separate partition and wrangled using symlinks.

If you want to move all cargo target dirs globally

AFAIK, this doesn't work because then all builds of Rust code on my machine is serialized on the lock in the one target directory (I already have issues with ALE competing with my :mak build commands in Vim as it is).

@bluss
Copy link
Owner

bluss commented Oct 4, 2019

I would half suggest that you should just use a personal excludes configuration in git for that. See core.excludesFile in git help config.

@mathstuf
Copy link
Contributor Author

mathstuf commented Oct 4, 2019

I'm aware of that; I use it for things like my Vim backup files and the like. But this is a file that "every" clone of this ends up having. It's basically a backport of the new behavior of cargo new: rust-lang/cargo#4944

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants