Xlinks to single files (VSS style)
We would like to convert from VSS to Plastic SCM, but VSS's file sharing works completely different than Xlinks in Plastic SCM (as far as I understood).
Firstly, there needs to be a possibility of creating xlinks to single files, just like in VSS. It is really important for us. We want to share single code files and single binaries between projects. Sharing the whole project (as a repository) when only its binary file is needed (or several code files) is no solution to us :-(.
Secondly, there should be two xlinks modes:
A link to a specified revision - just the way it is now (no changes).
A link always bound to the newest revision of the shared file (this is the way shared files work in VSS). This means than when somebody modifies a shared file and checks it in, all projects that use it in this mode should automatically update their xlinks so they are bound to the newly added revision of the shared file.
Why do we need it?
1. We share single source code files among different projects. We have very many files used this way and they are not necessarily associated logically with each other. Therefore, keeping them in a separate repository and sharing them all at once with projects that use only some of them seems illogical. Imagine there is a shared directory with 10 code files for handling different kinds of data sources (or databases). I want one of my projects to use a file that handles XML data source only, but I have to include all other files from that repository as well, because there is no other option :-(.
- We store our installation wizard configuration and its content files on VSS as links. Its directory structure contains links to binaries that are then built into a setup file. The binaries belong to different software projects. Whenever a software project is modified and checked in with its binaries, those binaries appear in the project's folder and at the same get updated in the installation wizard's directory structure of VSS. Thanks to that we do not have to update each binary file included in the wizard manually - they all get updated automatically whenever someone modifies them. So it is then enough to build the wizard and a setup file is ready to deploy.
Plastic SCM looks wonderful compared to VSS. I personally hate VSS, especially that I used to work on SVN which is incomparably better. However I've just come accross Plastic SCM and fell in love with it :-). I hope you will accept my kind request to make those changes. This software is really fantastic! I would love to use it, but you see the problems that keep us (as a company) from converting to it...
Xlinks to files doesn’t seem to be a popular idea and it almost breaks the underlying concept.
Göran Wallgren commented
Hi Diego, you can use cloaking (cloaked.conf) for that.
However, if you want to cloak an xlink folder make sure you cloak only the contents, and not the actual xlink folder! Rule syntax:
You can checkin the cloaked.conf in the root of your main repo but you should also put an identical cloaked.conf in your Plastic home dir (%LocalAppData%/plastic4 on Windows) to avoid pulling the cloaked files on initial Update / Switch in new workspace.
Diego H. Bustamante commented
is there a way to xlink (to repo) but use an ignore-like mechanism to tell pscm to not bother pulling certain files from the server? like all others except the one file you intend to link to?