I think I'm starting to get that now, but what about the "External
Definitions" and "Vendor Branches" mechanisms? Is there any penalty for
having multiple repositories when they contain inter-dependant projects?
Wes
-----Original Message-----
From: Tom Vergote [mailto:tom@tomvergote.be]
Sent: Tuesday, March 23, 2004 2:27 PM
To: Crucius, Wesley
Cc: 'users@subversion.tigris.org'
Subject: RE: Thanks and a global versioning question; WAS:: Help: XML Pars
er e rror, Date Conversion failed
On Tue, 2004-03-23 at 21:13, Crucius, Wesley wrote:
> 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?
Not really i think
Running svnserve -d -r c:\reporoot\ works just fine if under reporoot you
have a structure with subdirectorys (and repository's) per project.
The -r only restricts as far as i understood and you can still access each
different repo with svn://hostname/projectname if each project is a
repository of its own
You're right about administering users though
>
> 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
Received on Tue Mar 23 21:46:24 2004