[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

repository topography considerations

From: Fletcher Cocquyt <fcocquyt_at_stanford.edu>
Date: 2005-07-05 20:03:12 CEST

We have several (> 10, < 100) projects in CVS we'd like to migrate from a
flat CVS structure to SVN
We are using mod_auth_kerb to hook into campus Kerberos servers for
authentication - works fine.

We mulled over the implications of these topography choices:
1) All projects in one repo.
        Pros: one location to find everything - less admin overhead
        Cons: does not allow granular (per project auth) via mod_auth_kerb
Location directives since all projects are in the same fsfs location
2) Projects get grouped into their own repos based on logical user groups
        Pros: allows more granular auth per project class
        Cons: Can't easily move projects between repos and maintain history?
(this is not clear - looks like maybe a manual dump and load may work)?

Q: What are the best practices?
How are others deciding these issues?

Fletcher Cocquyt
Data Center Services
Sr. System Administrator
Information Resources & Technology
School of Medicine Stanford University
650-723-8390, option 6

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Jul 5 20:05:14 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.