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

[Feature Request] Track original path instead of assuming ~ #1

Open
abloom opened this issue Apr 2, 2012 · 5 comments
Open

[Feature Request] Track original path instead of assuming ~ #1

abloom opened this issue Apr 2, 2012 · 5 comments

Comments

@abloom
Copy link

abloom commented Apr 2, 2012

I would like to track files like ~/.ssh/config but Briefcase ignores the path and assumes everything is directly in the users home directory.

@jim
Copy link
Owner

jim commented Apr 14, 2012

I'll have to think about how to implement this. Right now Briefcase just assumes that anything in the dotfiles directory will be symlinked to from the root of the user's home directory. To handle files at arbitrary paths, we'd have to store some metadata about each file in another location.

@abloom
Copy link
Author

abloom commented Apr 15, 2012

why not just store them in your dotfile dir with relative paths?

~/.ssh/known_hosts -> ~/.dotfiles/ssh/known_hosts

@ixti
Copy link

ixti commented Sep 14, 2012

👍 But I would like to propose not to change initial path, just copy it "under":

~/.ssh/known_hosts -> ~/.dotfiles/.ssh/known_hosts

@RadicalZephyr
Copy link

👍 I just tried to put my .ssh/config file into briefcase and was surprised at the results...

@JDFagan
Copy link

JDFagan commented May 10, 2016

Relative paths are important I believe too to prevent name collisions for similarly named files (e.g., .ssh/config vs .aws/config). Seems like just keeping paths relative is good solution as mentioned above. Also, if one tries to go outside their home directory, then I guess could have special name like /foo/bar/.somedotfile -> ~/.dotfiles/root/foo/bar/somedotfile.

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

No branches or pull requests

5 participants