Quote:
Originally posted by ashwken
OK, so symbolic links allow you to have a relative path to a file that is physically stored outside the UR datapath.
1. How do symbolic links address the need of transporting those files from one machine to another, or moving the UR database and linked files to a usb drive (essentially another machine, where the usb drive is used to run UR and linked content independent of the originating system)?
2.Wouldn't those files that reside outside the UR datapath on machine-A need to reside in a duplicate folder structure on machine-B regardless of whether you used symbolic links (with a relative path) or UR Links with an absolute path - in order for either type of link to work on machine-B?
3. Also, although the symbolic link provides a relative path for UR, isn't the symbolic link actually pointing to an absolute address.
4. If machine-A has a D: drive, and machine-B does not, how is this resolved on machine-B (if you have the same folder structure on both machines, just on different drives)?
Again, I'm trying to understand under what conditions symbolic links would be useful.
|
1. they don't help in the transporting issue, but neither cause problem. They are just what they are, linking one place to another, just like you can have 2 items in UR in different places.
2. yes, that's why it's preferable for linked files to be under UR directory, and symbolic links helps if you actually want to store the files physically somewhere else. (in fact I asked kinook that the path could be relative as long as the file is on the same drive, not only under UR directory, eg. something like ../../test/tes.pdf)
3. yes
4. the links have to be created on machine B anyway, so it doesn't matter whether there is drive C or D or whatever, if you want to have the same directory structure.