Our current development installation uses one Subversion repository containing several projects, each of which has branches, tags, and connecting lines. Then we use the βrare checkβ to select the projects and branches of these projects for work.
As a result, the directory structure of the working copy is the same as the structure of the repository, including branch information, and we never use it svn switch. (This style of work is likely to be familiar to anyone who uses SVN, but may surprise those who do not.)
We are thinking of using Composer to manage external and internal dependencies, but I'm not sure how this can work with a sparse work style.
I would like some way of using the directory in an existing check to satisfy dependencies, and not to every "root project" that needs a separate copy.
For instance:
- Sites / Foo / Trunk
- depends on lib Aaa, so links lib / Aaa / trunk
- depends on lib Bbb 1.5. *, therefore links lib / Bbb / branches / release-1.5
- Sites / Bar / Trunk
- depends on lib Aaa 1.0. *, therefore links lib / Aaa / branches / release-1.0
- depends on lib Bbb 1.5. *, therefore links lib / Bbb / branches / release-1.5
Currently, if I edit the code in lib / Bbb / branch / release-1.5, I can test these changes on both sites without having to commit it and update another.
Can Composer be used to manage these dependencies?
(PS: Please do not answer "refuse SVN, use Git, this is awesomez", this is the answer to another question.)