<div dir="ltr">actually here's the article explaning the symlink in dropbox disaster: <a href="http://www.paulingraham.com/dropbox-and-symlinks.html">http://www.paulingraham.com/dropbox-and-symlinks.html</a><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Jan 8, 2017 at 2:35 PM, Timothee Cour <span dir="ltr"><<a href="mailto:thelastmammoth@gmail.com" target="_blank">thelastmammoth@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><a href="https://github.com/dlang/dmd/commit/801742d93ecb6c929409a19c024dd87ca25330a3" target="_blank">https://github.com/dlang/dmd/<wbr>commit/<wbr>801742d93ecb6c929409a19c024dd8<wbr>7ca25330a3</a> introduced a symlink dmd repo; if a user clones it inside a Dropbox (or google drive) and syncs his dropbox to another machine, it will create havoc:<br><div><br></div><div>* google drive doesn't support symlinks at all</div><div>* dropbox supports it in a horrible way, resolving symlinks, leading to duplicating the folder that's being symlinked on the 2nd machine: <a href="http://askubuntu.com/questions/452714/is-dropbox-going-to-always-resolve-my-symlinks" target="_blank">http://askubuntu.com/<wbr>questions/452714/is-dropbox-<wbr>going-to-always-resolve-my-<wbr>symlinks</a>, </div><div><br></div></div>
</blockquote></div><br></div>