FYI, symlinks exist in Windows since ntfs 3.0 under the name of "junctions", though only for directory targets.
See http://en.wikipedia.org/wiki/NTFS_junction_point On Tue, 2011-03-15 at 11:45 -0400, Joey Hess wrote: > Alternatively, windows versions of these functions could be found, > which are all the ones that need POSIX, I think. A fair amount of this, > the stuff to do with signals and users, could be empty stubs in windows. > The file manipulation, particularly symlinks, would probably be the main > challenge. > > addSignal > blockSignals > changeWorkingDirectory > createLink > createSymbolicLink > emptySignalSet > executeFile > fileMode > fileSize > forkProcess > getAnyProcessStatus > getEffectiveUserID > getEnvDefault > getFileStatus > getProcessID > getProcessStatus > getSignalMask > getSymbolicLinkStatus > getUserEntryForID > getUserEntryForName > groupWriteMode > homeDirectory > installHandler > intersectFileModes > isRegularFile > isSymbolicLink > modificationTime > otherWriteMode > ownerWriteMode > readSymbolicLink > setEnv > setFileMode > setSignalMask > sigCHLD > sigINT > unionFileModes > > _______________________________________________ > vcs-home mailing list > vcs-home@lists.madduck.net > http://lists.madduck.net/listinfo/vcs-home _______________________________________________ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
