2 ms·
How is this different from before? All my symlinks reside at odd (but convenient for me) locations in my file system outside my Dropbox folder. They all point t
by dreamcompiler 7y ago
How is this different from before? All my symlinks reside at odd (but convenient for me) locations in my file system outside my Dropbox folder. They all point to locations inside my Dropbox folder. Everything works perfectly, unless I make the mistake of creating a symlink inside Dropbox that points out; those have always exhibited strange behavior so I stopped using them long ago.
- eslaught 7y agoIt used to be that if you created a symlink (even an internal symlink) it would result in storing a duplicate of the symlink target instead of the symlink itself. On the first machine, it would preserve the symlink, but on any subsequent machines it would store a copy of the file. You could restore the symlink by hand on other machines, and it wouldn't interfere with syncing, but you had to do it manually. With the old Dropbox, if you did the following: 1. machine A: clone a git repo that contains a symlink 2. machine B: wait for repo to sync 3. machine B: git status You'd see a "type change" in the git status output. If you did git checkout you'd get your symlink back and it wouldn't interfere with machine A. Which was all fine if you had your file contents synced in git or similar, but if you had it set up by hand it was a huge pain in the rear (because you'd have to locate the bad symlinks and restore by hand manually).