Using VW on a network - Best Practices

[islandmon]

quoted from svn-book

Versioning symbolic links

On non-Windows platforms, Subversion is able to version files of the special type symbolic link (or, ?symlink?). A symlink is a file which acts as a sort of transparent reference to some other object in the filesystem, allowing programs to read and write to those objects indirectly by way of performing operations on the symlink itself.

When a symlink is committed into a Subversion repository, Subversion remembers that the file was in fact a symlink, as well as to what object the symlink ?points?. When that symlink is checked out to another working copy on a supporting system, Subversion reconstructs a real filesystem-level symbolic link from the versioned symlink. But that doesn't in any way limit the usability of working copies on systems such as Windows which do not support symlinks. On such systems, Subversion simply creates a regular text file whose contents are the path to which to the original symlink pointed. While that file can't be used as a symlink on a Windows system, it also won't prevent Windows users from performing their other Subversion-related activities.

[wezelboy]

To create a symbolic link you will need to use the terminal. It can be found in /Applications/Utilities/

To link your local Prefs_Def to a server based one, you need to do the following:

First you need to remove the local Prefs_Def (but make sure you have a backup somewhere)

In the terminal type the following: ln -s

a sample command would look like:

ln -s /Applications/VectorWorks\ 12.0.0/Plug-Ins/VW_Arch/Data/Prefs_Def /Volumes/Server/Preferences/Prefs_Def

Note: The forward slash after VectorWorks is important, as the directory name in this example has a space in it. This way the shell will parse the space as part of the name and not as an argument seperator.

You might need to futz with the permissions of Prefs_Def on the server to get it to work correctly.

Edited August 16, 2007 by wezelboy