The reason most people advise to do separate repositories is because it separates out changes and change sets. If someone makes a change to the client projects (which you say doesn’t really effect others), there is no reason for someone to update the entire code base. They can simply just get the changes from the … Read more
Some subversion repositories will group logically unrelated things (i.e. projects with different version numbers and release cycles) under one trunk: . |– branches | |– project-a-1.x | `– project-a-feature-1 |– tags | |– project-a-1.0 | |– project-b-1.0 | `– project-b-1.1 `– trunk |– project-a `– project-b This kind of layout has no direct analog in … Read more
I find that the Subversion Repository Layout blog post summarizes this pretty well: (…) there are several common layouts that have been adopted by the community as best practices and therefore one could think of these as recommendations. If your repository is accessible to the public, following these conventions might make it easier for users … Read more