On Tue, Nov 3, 2015 at 7:59 PM, David Mason <[email protected]> wrote:
> > It's simple: a symlink is a filesystem artifact and should be reflected as > such in the repository. It should not be followed; if foo is a symlink and > I say "fs add foo/bar" it should probably give an error. (This might > surprise people the first time, but it's easy to explain - foo/bar isn't > part of the repo, regardless of where foo points.) > But it's not quite that simple, philosophically speaking: we expect Fossil to extract _exactly_ what we put in it, and that's not portably possible when it comes to symlinks. As soon as someone checks out your repo on a non-Unix system, fossil is creating output which you did not put in fossil. That's a tremendous psychological/philosophical hurdle for me. i'd rather live without symlinks than know that my repos check out differently depending on the platform. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal "Freedom is sloppy. But since tyranny's the only guaranteed byproduct of those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
