It sounds like in your case the projects are completely independent and
un-related to one-another, right? In my case, I have one set of projects
which are analogous to applications code and another set of projects that
are analogous to operating systems. There are dependancies for each
"application code" project upon specific versions of the "operating system"
projects. Because of this, I think I wanted to be able to utilize the
"external definitions" and/or "vendor branches", which I thought was going
to be a problem with multiple repositories... I'm starting to think I'm
wrong about that asumption?
Wes
-----Original Message-----
From: Jason Dunham [mailto:jdunham@SFIS.com]
Sent: Tuesday, March 23, 2004 2:25 PM
To: Crucius, Wesley; users@subversion.tigris.org
Subject: RE: RE: Thanks and a global versioning question
I'm both lurker and newbie, so forgive me if I'm stating the obvious, but
this question keeps coming up over the last few days.
But it's no big deal to run separate "repositories" on a single svnserve
server. Each of my customers/projects gets a separate repository, but it's
all in one top-level folder on a single hard drive. For each new project, I
cd to the top level folder on the server, and create a new repository using:
svnadmin create <newproj>
then I set the access lists for the users I want to give access (using the
svnserve.conf file) svnserve is running with option -r /top/level/folder
Then for the import, I create a new a new folder containing branch, trunk,
and tags subfolders, copy the source code into trunk, and then import import
the new folder [I use tortoisesvn] into
svn://server.myco.com/newproj
and give this URL to anyone else who is cleared for access to that project.
The revision numbers remain separate for each of my projects.
Jason Dunham
-----Original Message-----
From: Crucius, Wesley [mailto:WCrucius@sandc.com]
Sent: Tuesday, March 23, 2004 12:14 PM
To: 'users@subversion.tigris.org'
Cc: 'Tom Vergote'
Subject: RE: Thanks and a global versioning question; WAS:: Help: XML Parser
e rror, Date Conversion failed
Well, at least I'm not [completely] crazy... Although, I don't like the
fact that I'd have to maintain/administer multiple repositories and that it
would break the "External Definitions" and "Vendor Branches" capabilities, I
think... Also, if using svnserve, it's not possible to run multiple
repositories (instances of svnserve) on a single server, is it? Well, unless
I bind each instance to a different port number, which seems hokey. It's
cerainly not a show stopper for me if I have to run Apache, but setting up
svnserve certainly is simple in comparison. Am I correct to assume that
using Apache would make it possible to have multiple repositories without
having apache listening on multiple ports?
Wes
-----Original Message-----
From: Tom Vergote [mailto:tom@tomvergote.be]
Sent: Tuesday, March 23, 2004 2:02 PM
To:
Subject: Re: Thanks and a global versioning question; WAS:: Help: XML Parser
e rror, Date Conversion failed
On Tue, 2004-03-23 at 20:26, Crucius, Wesley wrote:
> [snip]
> My proposed users aren't going to like (or
> understand) the global revision number
I'm facing the same problem and that's why i'm considering a repository per
project, "the project gets a new revision every time someone commits" seems
easier than "something in the repository got committed so everything has a
new revision now, and thats why that project jumped to rev 317 even though
it's still only a html design"
> [snip]
> Any thoughts?
>
> Thanks again,
> Wes Crucius
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 23 21:50:54 2004