Note: If you edit the flow too much, the question loses it's context and can be quite difficult to follow...
> -----Original Message----- > From: Tech Geek [mailto:techgeek12...@gmail.com] > Sent: 01 September 2010 21:02 > To: Subversion Users > Subject: Multiple Repositories under one subversion daemon > > I am running subversion server on a Windows machine. Right > now I am in the process of converting my exisiting projects > to start using subversion and my projects are located at > different paths/locations. For example: > C:\data\project1 > C:\project\bluecat > C:\software\abc > > Now it seems that wehn we start svnserver executable it > accepts the root path of the repositories like this: > > svnserve.exe --daemon --root drive:\path\to\repository\root > > However in my case all my projects are under different > locations and unfortunately I cannot move them under one > location because lot of other systems are expecting those > projects to be at that location. So I would rather change the > new system (svnserver) to adopt to the exisiting layout. > > Is there any way to get around this? > <other missing replies> > -----Original Message----- > From: Tech Geek [mailto:techgeek12...@gmail.com] > Sent: 02 September 2010 00:40 > To: David Bartmess > Cc: users@subversion.apache.org > Subject: Re: Multiple Repositories under one subversion daemon > > If I understand you correctly this would mean that somebody > (user/developer) has to checkout the code for each of the > projects from the repository location (say > C:\svn\data\repositories) to: > > C:\data\project1 > C:\project\bluecat > C:\software\abc > > so that the above locations reflect the latest code? > A subversion repository cannot be used directly for tasks such as building the project, it is a safe location for storing all the history of the project files. You then 'check out' a "working copy" of the project (from the latest or any historical point in time) to pretty much anywhere you fancy and do your work there. Most subversion repositories are on centrally managed (and backed-up) servers remote from the actual development / deployment work because you want to safeguard your precious source code... So, yes, the subversion repository must be somewhere other than your current "working copies" and some task (developer or automated) would be responsible for keeping these projects up to date. To assist in this, subversion provides "hooks" that can and are used for just such tasks. Have you read the free online subversion book? The first few chapters are a great introduction to source code control: http://svnbook.red-bean.com/nightly/en/index.html I hope that helps, ~ mark c
