On Oct 16, 2017, at 4:44 PM, Arseniy Terekhin <sen...@gmail.com> wrote: > > What should "ln" do on FAT16/32 and exFAT filesystems? Well, I'd just expect > fossil to not bother creating any links and maybe give a warning.
Or, write two copies of the file, then on checkin either: a) take the later of the two files as the new truth; or b) ignore changes to the linked-to file, and accept changes only to the linked-from file. See, not so simple. > On Windows XP+ I'd expect native NTFS links. That’s even more complex, because Microsoft in their infinite wisdom chose to make symlink creation a privileged action by default, requiring Admin privs out of the box. And I don’t mean UAC here, I mean “Run as administrator.” There’s some kind of policy setting to change this, but then you’d be requiring that every Fossil user make that change if they want to allow symlinks. And then on top of all that, the MKLINK cmd.exe command takes its arguments backwards relative to ln, cp, COPY… It’s like they didn’t want you to use this feature, that they put it in only to stop people asking for it. You know, at this point I think I’d accept *.lnk files. At least Explorer copes with them, and it would avoid the conundrum from the first part of this email. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
