Setting up a repository that makes sense.

[Samuel Winchenbach <he...@kelpworks.com>]

Hi Everyone.

I am having a bit of trouble with the revision numbers in svn.

This is the situation I have..

In the company I work for we have projects that have several applications (managers, user clients, and servers) and I would like to set up a repositry in the following manner.

I want each application of the project to have it's own revision number.  So if I update the update the manager revision it does not effect the revision of the user client.  I also would like to be able to tag each application individually.

This would mean I would need a seperate repository for each application, correct?

BUT...  I would also like to make tags (releases) of the project which would be constructed from the tags (not the trunks) of the individual applications.  This seems difficult to do.

First of all, does this make sense?

If I was creating a set of applications called "Widget Factory 2004" that project might be made of "Widget Server tag release 457" and Widget User Client tag release 931"... etc

And the final question is... if it does make sense can anyone suggest an easy, or at least a method that makes sense?

Thanks.

Samuel Winchenbach 
B.S. Electrical Engineering
hermitcrab@kelpworks.com

Re: Setting up a repository that makes sense.

[Ben Collins-Sussman <su...@collab.net>]

On Fri, 2004-07-23 at 20:40, Samuel Winchenbach wrote:

> This would mean I would need a seperate repository for each
> application, correct?

Correct.

> 
> BUT... I would also like to make tags (releases) of the project which
> would be constructed from the tags (not the trunks) of the individual
> applications. This seems difficult to do.

You can certainly write 'release' scripts that checkout tags from
different repositories, and arranges them into some sort of tree that
you distribute.  Is this what you're talking about? 

> 
> First of all, does this make sense?

Not really.  Just put everything in one repository.  People seem to
freak out (at first) that the global revision number is constantly
changing, even if their project doesn't change.  It doesn't matter. 
Really.  You learn to ignore it.  Revision numbers are just names of
commits;  it has nothing to do with the "version" of any particular
project.  Don't be afraid of it. 

Take a look at the ASF repository:  it has dozens of different projects
in one repository, and it works great.




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org