On Thu, Jan 27, 2011 at 12:13 PM, Dmitry Chestnykh <dmi...@codingrobots.com> wrote: > > - Shortcuts on Windows are mostly for users -- that is, programs > don't handle them as well as Unix programs handle symlinks (by > following them by default).
I had forgotten that. As I recall, open() on a symlink automatically follows the link(s) and opens the (ultimate) target. (At the moment, not convenient to check how path with a short cut in it is handled.) > - In case of cross-platform programs, what if we want to store the > actual shortcut in the repository, and don't want it to be > converted to a symlink on Unix? In this case, how Fossil will decide > if we have an actual shortcut or "symlink-shortcut"? This same question could be asked of symlinks, whether the project is multiplatform or not. In the case the target of the short cut is a directory, I do not see why one would not want the symlink created. As for non-directory targets, it would not be unreasonable to not create symlinks, but rather just create a placeholder file with a .lnk extension. > - We would be tied to handling .lnk extension as a special case. Unfortunately, for those of us dealing with Window, the .lnk extension is already a special case. I do not like that that is necessary, so I can understand you not liking it, either. > but Windows shortcuts contain separate properties for the > target file and the "Start In" directory. If the latter parameter is > not entered, attempting to use the shortcut may generate "missing > DLL" errors not present when the application is accessed directly I do not think this issue would apply when the target is a directory. > I think this case would be best handled by something like Git > sub-projects, if Fossil had this feature. This feature would have the benefit of avoiding the need to do multiple check outs, but having a sepperate working copy for each subproject would allow the working copies of multiple projects to share the subprojects at the working copy level, rather than requiring a subordinate working copy of each subproject within each project's working copy. This reasoning applies equally both to Unix/Linux/BSD/POSIX symlinks and to Windows short cuts. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
