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

Re: Multiple projects on one system?

From: Alessandro Sabatelli <planoform_at_gmail.com>
Date: 2005-11-29 04:42:33 CET

awesome!!! this is just the info i was looking for. is this type of
real-world usage info in the svn book? i looked and can look again, i just
didn't see it...

On 11/28/05, Bruce Webber <brucewebber@fastmail.us> wrote:
>
> --Hal Vaughan <hal@thresholddigital.com> wrote:
>
> > I have a suite of programs I've created that includes the server
> programs
> > that retrieve and sort data, a client program that goes on other
> > people's computers, a setting editor, and a few configuration
> > directories. I'm self taught, so I set everything up as it worked for
> > me as I learned and did more. I have one master directory, then,
> within
> > that, I have directories for the executables for the server. Also
> > within the master directory, I have directory trees for the client
> > program and setting editor, as well as different directories for
> > configuration files.
> >
> > It appears to me that if I want to include all of these in Subversion,
> > I'd have to do it as one project. I'd prefer, if possible, to have 4
> > separate projects. When I look at examples in the book though, where a
> > file is committed by a name to a specified repository, I'm not clear if
> > that is enough for Subversion to keep them all separate as different
> > projects.
>
> Subversion does have any "concept" of a project. Within a repository there
> are folders. Each folder could considered be a separate project; that
> depends on the meaning you assign it and how you use it.
>
> >From what you've described, it would make sense to have all of your code
> in
> one repository. You already have it divided into folders for the server
> piece, the client piece, the editor, etc. You will be able to check out
> any
> portion of the system that you want, by specifying the folder.
>
> Assuming you might release a new version of the server code without having
> to change the client code, and vise versa, I suggest the following
> structure:
>
> repository
> server
> trunk
> branches
> tags
> client
> trunk
> branches
> tags
>
> etc.
>
> [...]
>
> > So is keeping a number of separate projects on one system in subversion
> > easily doable?
>
> Definitely. Each project lives in a separate folder.
>
> --
> Bruce Webber
> brucewebber@fastmail.us
> http://brucewebber.us
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
Received on Tue Nov 29 04:44:34 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.