Version Control with Subversion - Login

Repository Administrationthem in groups inside the repository, perhaps putting projects with similar goals or sharedcode in the same subdirectory, or maybe just grouping them alphabetically. Such an arrangementmight look like this:/utils/calc/trunk/tags/branches/calendar/trunk/tags/branches/…office/spreadsheet/trunk/tags/branches/…Lay out your repository in whatever way you see fit. Subversion does not expect or enforcea particular layout—in its eyes, a directory is a directory is a directory. Ultimately, youshould choose the repository arrangement that meets the needs of the people who work onthe projects that live there.In the name of full disclosure, though, we'll mention another very common layout. In thislayout, the trunk, tags, and branches directories live in the root directory of your repository,and your projects are in subdirectories beneath those, like so:/trunk/calc/calendar/spreadsheet/…tags/calc/calendar/spreadsheet/…branches/calc/calendar/spreadsheet/…There's nothing particularly incorrect about such a layout, but it may or may not seem asintuitive for your users. Especially in large, multiproject situations with many users, thoseusers may tend to be familiar with only one or two of the projects in the repository. But theprojects-as-branch-siblings approach tends to deemphasize project individuality and focuson the entire set of projects as a single entity. That's a social issue, though. We like our originallysuggested arrangement for purely practical reasons—it's easier to ask about (ormodify, or migrate elsewhere) the entire history of a single project when there's a single repositorypath that holds the entire history—past, present, tagged, and branched—for thatproject and that project alone.Deciding Where and How to Host Your RepositoryBefore creating your Subversion repository, an obvious question you'll need to answer is124