On Jan 28, 2011, at 18:18 , Dmitry Chestnykh wrote: > On Jan 28, 2011, at 6:03 PM, Remigiusz Modrzejewski wrote: > >>>> In that case the F-card access permissions could be extended further with >>>> "ld" for link to directory and "lf" for link to file when the link is >>>> first imported into Fossil. This would matter only when the link is >>>> created in a working copy on Windows. >>> >>> But the target file or directory could not exist at all, so it won't solve >>> the problem. >> >> But why call it a problem? There can also be #include <boost/foreach.hpp> >> inside a C++ file that refers to a header that does not exist at all. Why >> don't we try to solve this problem as well? > > > I think you misunderstood, let me try to explain: > > On Windows, to create a link we must pass a flag to > CreateSymbolicLink() function to tell it if we want a link to a file > or a directory. Imagine we add a symlink on Unix, which points to > ../README, which doesn't exist. When we checkout this repository on > Unix, we just re-create this symlink. But on Windows, when re-creating it, > should we create a link to a directory or a file?
Ah, yes, I misunderstood. But, isn't creating a symbolic link to something that does not exist on the committer's system a very rare corner-case? If so, we can go the easy path and require him to explicitly specify that while committing. Kind regards, Remigiusz Modrzejewski _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
