On 08/05/07, Julian Kolodko <Julian.Kolodko@silverbrookresearch.com> wrote:
> >> We have a project that was originally created under Linux. The top
> >> level directory was populated using hardlinks and the entire
> >> structure was checked into a repository. I am now trying to check
> >> this structure out onto a windows machine but the hardlinks are not
> >> being translated into something that windows understands. Each
> >> hardlink is replaced with a text file that says where the target file
> >> is e.g.:
> >> link ../runup/device_m.v
> >> Actually, it seems there is a chain of links. If I look at the file
> >> specified above I get:
> >> link ../analog/model/device.v
> >> Obviously I can't compile this - I need to get all the "real" files
> >> into the top level directory - I'd have to follow the chain of links
> >> to get to the real file, then copy that file back to the top level
> >> directory. This will be tedious for the 100 or so files at the top
> >> level. Is there any automated way of doing this in tortoisesvn??
> > How would that work?
> > Such a link can point to any location. Even locations that don't exist
> > on windows (and the paths too are not windows-paths but linux paths).
> > I suggest you remove those hardlinks and restructure your working copy
> > setup. Hardlinks are really not the way to go here.
> The structure is a self contained hierarchy of subdirectories (i.e.
> hardlinks in the top level directory point to files in subdirectories) -
> all the directories/files in the structure have been checked in to the
> repository and the structure can successfully be checked out under
> Linux. Things only go haywire if you try and check out the structure
> under windows because windows doesn't understand the links. To me it
> seems that SVN understands what a hardlink is, it just doesn't treat
> that link properly when you checkout to a windows machine.
Well the Linux client understands how to handle hard links, but the
Windows client doesn't, because Windows does not support them. If you
try the subversion command line client you will find the same thing.
You would have the equivalent problem on Linux if you used Windows
The obvious rule is: if you want your WC to work under different OS
types, don't build in this sort of OS-dependency.
If you really want to continue this argument, the place to do so is on
the subversion users list because it is the subversion library which
creates the items in the working copy.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Wed May 9 00:41:58 2007