Discussion Forum

versioning by soft/hard-links

To add questions or replies, please log in.



Filter:

Post author:
Text in post
Post date from: to: (dd.mm.yyyy)
 
versioning by soft/hard-links
I tried to set up versioning in case of an assembly in the following way (so that parts of the assembly can have independent versioning):
- different versions of a part are stored in different files, their names carrying the version number, for example partA.1.dwb (where 1 is the version number)
- the actual version of a part is realized via a symlink (Linux): partA.dwb --> partA.1.dwb
- the part is included in the assembly via the symlink (i.e. File-->Insert objects from file-->partA.dwb)

This way one could
- have several different versions of the parts, all of the old ones kept on disk
- very easily change the versions of the parts in the assemblies (i.e. just make the symlink to a different version)
- clearly see which is the current version (ls -l)

The problem is that VariCAD seems to overwrite the symlink file itself, instead of the symlink target (i.e. the symlink file becomes a regular file, and the 'link' disappears)

I think that with hardlinks it would work (still to be tried), but the problem there is that it's not so easy to visualize, which is the current version (i.e. to which version the hardlink points to)

Any comments on this? Could this behaviour of VariCAD be changed? Or are there any other plans to introduce versioning in VariCAD?
Thanks
versioning by hard links
It seems that it does not work even with hard links: when I open/modify/save a part file, which is in fact a hard link to another file, the two files will be different. It means to me, that VariCAD *removes* the file first, and then writes into it, by this breaking the link (if it would just open the file for writing/updating, it would also effect the other link, if I am not wrong...)

1