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

Organizing SVN reposities

From: Han The Man <hantheman12_at_hotmail.com>
Date: 2003-06-17 17:36:02 CEST

Dear SVN experts,

I'm in the process of implementing SVN in our company, along with ViewCVS
and TortoiseSVN.

In that regard, I have a couple of questions:

1) I'd like to put everything we have under version control - including
source code, documentation (MS Office files, etc) and binary files for
release to customers. So there will be many large, binary files. Any
problems with this approach?

Should we, due to the potential large size of all project files, use one
repository for each project, one repository for related projects or just one
repository? Any suggestions would be welcome.

3) Some releases (or branches) of a given product may depend on other
versions of 3'rd party libraries than other releases. Is it reasonable to
put even these libraries in SVN? It would be nice to have everything needed
by a given release in a single place. Again, I suppose size would be a

P.S. Thanks for a FANTASTIC scm system. For us, SVN means a most welcome
goodbye to CVS and SourceSafe.

MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 17 17:36:53 2003

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

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