Sharing code between repositories

[pnixon]

What's the best practice on sharing code between repositories in Plastic SCM?  We were thinking of using XLINK, however according to the most recent release notes it would seem that's not the solution (see quote below).

 

<quote>

 Scenario: create two xlinks pointing to the same rep.

    When trying to perform an update, it fails.

    It's not possible for PlasticSCM to perform an update operation having two

    or more xlinks pointing to the same repository. It's not allowed to load

    the same item in multiple workspace paths.

</quote>

[manu]

Hi!

 

yes, the right way to share code between repositories comes trough using xlinks.

But it has some limitations, you cant have a repository with several xlinks targeting the same repository since you will be loading duplicated items in your workspace.

 

Here you have some examples about using xlinks:

http://www.plasticscm.com/releases/4.1/manuals/en/xlinksguide.pdf 
http://codicesoftware.blogspot.com/2011/12/how-to-link-repositories-using-xlinks.html 
http://codicesoftware.blogspot.com/2012/06/xlinks-and-branch-per-task-in-dvcs.html

[zz74b]

Is there a way to have an XLink always refer to the latest code in the trunk of a repository, rather than targeting a particular changeset?

My use case:

I have build scripts that are xlinked to by other repositories. I don't want to have to update the xlinks in all the repositories using them each time a minor change is committed to the build scripts trunk.

[manu]

Out of the box it's not possible.

 

You can create a script to do it, a tray application or something.