On Mon, Nov 2, 2015 at 5:01 PM, Ron W <[email protected]> wrote: > On Mon, Nov 2, 2015 at 6:38 PM, Scott Robison <[email protected]> > wrote: >> >> From https://en.wikipedia.org/wiki/NTFS_symbolic_link#Restrictions: The >> default security settings in Windows Vista/Windows 7 >> <https://en.wikipedia.org/wiki/Windows_7> disallow non-elevated >> administrators and all non-administrators from creating symbolic links. *This >> behavior can be changed running "secpol.msc" the Local Security Policy >> management console (under: Security Settings\Local Policies\User Rights >> Assignment\Create symbolic links). It can be worked around by starting >> **cmd.exe >> <https://en.wikipedia.org/wiki/Cmd.exe> with Run as administrator option or >> the runas <https://en.wikipedia.org/wiki/Runas> command.* >> > > Where I work, we would to ask IT to modify the policy for us. Given how > many years it took of them having to install the specialized tools we in > Product Engineering need before IT agreed to grant us local admin privs, I > would expect similar. > > I suppose runas could be used in BAT files (much like sudo can be). > > But, as I said in another post, we have been able to get away from > symlinks by using the vpath feature of GNU make. >
In my work as well it is often a chore to get IT to change corporate enforced policies, so this might not be an option in some environments. As for me and my own development, however, I can easily get fossil to create symlinks with my winsymlink branch as long as I can get an elevated prompt or can get a non-admin user with symlink rights. I guess what I'm saying is that most of the effort has already been expended on Windows symlink support. At this point I think it's just permissions. -- Scott Robison
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
