I am just wondering if the following scheme might work: - N repositories for N different, unrelated projects - 1 directory containing symlinks to those N repositories - pointing client to this 1 fake repo
Reason: to allow different repo numbering for unrelated projects.
My gut feeling is that this won't work: I've never heard of anyone doing it, and the SVN book doesn't lead me to believe that it's possible. Nevertheless, someone with more experience may prove me wrong.
What don't you like about connecting to different repositories when you want to work with the project in each one? Are we talking about a large number of repositories if you go with one project per repository?
I think that best approach for you, given the concerns that you've expressed about repository revision numbers, is to try using SVN both ways. Set up one repository with a few dummy projects and commit a few changes to some of them. Then, repeat the experiment with a few repositories each containing one project. The projects don't need to be "code" projects; they could just be a collection of one or a few text files that are easy to change for the sake of the experiment.
Ali, I'm not sure if i understood your question properly. Is it like saying, Struts 1.2 works with Some Commons package 1.1 version and i want them linked because Struts 1.2 might not woth with a later version of the commons package but at the same time i want to pick up all additions / changes to commons package 1.1?
May be i'm wrong but is this what you are trying to acheive?
The scenario I have proposed (still haven't got the time to test it) is meant for allowing the clients use the same repository url. But as subversion uses a unique repository number for versioning and I want to have different versioning numbers (as the projects are completely independent) I will have to have more repositories.
Ready for the final note: it is working :-). I have done the following: - created different repositories (containing one or more projects each) - created a svnrepositoryroot directory which contains as subdirectories symlinks to each project name (symlinks on windows ntfs can be easily obtain with junction tool) - clients are working using as url <start_url>/svnrepositoryroot/project_name
What I have accomplished by this? 1/ have related projects versioned the same (located inside the same real repository) 2/ access to all repositories through an unique url_root
Drawbacks: the single drawback i can see is if there are 2 projects with the same name in different repositories (quite a small chance).
pls let me know what do you think about the aboves.