-
Notifications
You must be signed in to change notification settings - Fork 2
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
Comments
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. |
why not just store them in your dotfile dir with relative paths?
|
👍 But I would like to propose not to change initial path, just copy it "under":
|
👍 I just tried to put my .ssh/config file into briefcase and was surprised at the results... |
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. |
I would like to track files like
~/.ssh/config
but Briefcase ignores the path and assumes everything is directly in the users home directory.The text was updated successfully, but these errors were encountered: