On Nov 1, 2015 6:09 PM, "Ron W" <[email protected]> wrote: > > On Sun, Nov 1, 2015 at 4:14 AM, Stephan Beal <[email protected]> wrote: >> >> But if it only stores a pointer, and requires the user to reconstruct the link, it's not terribly useful/friendly. The user would potentially have to replace fossil's placeholder pseudosymlink file with a link of his own (which he could point somewhere else than fossil thinks it "should" be). He might has well simply have a "post-checkout" script which sets up his symlinks for him. To me, that's the "proper"/"safest" way to handle symlinks in a repo (but i'm willing to accept being in the minority on that point). > > > On MS Windows, that is how it has to be done. Symlinks require the user be an admin and use a special command that is separately installed.
1. There is a winsymlink branch. I haven't merged from trunk too recently, but it does (as far as has been tested) provide equivalent symlink processing for Windows. 2. Normal non admin users can create symlinks. Admin users in a non elevated context cannot. Admin users in an elevated context can. There is a way to tweak defaults to allow all to be able to create symlinks. Thank MS for the inexplicable hoops admin users must jump through.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
