RE: Pros and cons of significantly large repositories

Matt,

Quoting the Subversion website (http://subversion.tigris.org
<http://subversion.tigris.org/> ), "The goal of the Subversion project
is to build a version control system that is a compelling replacement
for CVS in the open source community."

Quoting the CVS website (http://www.nongnu.org/cvs/), "CVS is a version
control system, an important component of Source Configuration
Management (SCM). Using it, you can record the history of sources files,
and documents."

I agree that most people use version control for application code bases,
however, I think you will find that many people use it for its intended
purpose: to track changes in whatever documents/files you deem important
to review and maintain over a length of time by multiple people. If you
don't care about history and being able to revert mistakes, then by all
means use rsync and keep the files on your filesystem outside of
Subversion. I don't see how Subversion or any version control system is
a "code only" tool and I believe most people would agree with that.

Andrew R Feller, Analyst

University Information Systems

Louisiana State University

afelle1@lsu.edu

(office) 225.578.3737

________________________________

From: Matt Sickler [mailto:crazyfordynamite@gmail.com]
Sent: Monday, April 09, 2007 12:57 PM
To: Andrew R Feller
Cc: users@subversion.tigris.org
Subject: Re: Pros and cons of significantly large repositories

subversion was meant to version source code, not distribute notes and
binaries
another tool such as rsync would be better at the latter

On 4/5/07, Andrew R Feller <afelle1@lsu.edu> wrote:

Hi,

My company is currently trying to use Subversion not only to store code
for new projects but also dumping of binary builds and internal
documentation (processes, meetings, etc). The question most often asked
is "Are you going to use a single repository or multiple repositories?"
I know a Subversion repository can hold any amount of data, but I want
to know is:

What are the pros and cons for having really large repositories versus
multiple, smaller repositories?

What experiences have people had with repository administration and
general usage that have made a particular choice good or bad?

I appreciate your feedback and insight!

Regards,

Andrew

 
Received on Tue Apr 10 14:36:25 2007