CVS to SVN Repository info

[Patrick Nelson <pn...@neatech.com>]

FC1 SVN-1.0.5

One of the things that we did with CVS was use the version tag that is
issued with a check in.  This did an auto versioning for us that we
liked and have gotten use to (MOC stuff here).  I understand that SVN
does repos level versioning which I'm not sure how to do a best practice
with.  So here is my scenerio:

I have a CVS repos with many many developement projects in them, all
under a meaningful directory structure.  So the repos would be like:

<path2repos>/sh
<path2repos>/pl
<path2repos>/py
<path2repos>/tcl
<path2repos>/c
<path2repos>/cpp
<path2repos>/sql

and then under each of those dirs would be directories for each of our
projects, such as:

<path2repos>/sql/storm
<path2repos>/sql/mmail
...
<path2repos>/c/gsalt
<path2repos>/c/fwa

This worked well for me and my team because it grouped like projects
together for more RAD level dev.  Tags were used only for final
releases.

I'm trying to setup the SVN repos so that it works well with the way we
have gotten use to working yet addresses more of what SVN has to offer. 
So my question is what is the best way to set up a repos that treats
each project (or module as it were in CVS) as its own entity and have 
easy access to a group of projects such as listed above.

I've used the basic migration script:

 cvs2svn.py -s <path2svnrepos>/sql <path2cvsrepos>/sql/

and this creates the <path2repos>/sql with trunk, branches, and tags
subdirs.  And then under each of these is the specific project subdirs. 
However, this removes any use of the SVN revision number like the CVS
revision number could be used.

I've thought about making each project a SVN repository in and of itself
which seems to be the best way to do it...  But I thought I would ask
you all to see if maybe I'm missing something.  Any suggestions would be
appreciated.  










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

Re: CVS to SVN Repository info

[Felix Collins <fe...@keyghost.com>]

> 
> SVN uses the repos as the overall version change.  Like I said I don't
> know what is the best way to do projects in SVN.  Is it to do a repos
> for each project or group them?  If group them, then what would the
> suggested structure be?  


I just set up subversion for our development group a couple of months 
ago.  I started with multiple projects per repository because it seemed 
easier admin wise. Especially as the SVNParentPath directive had issues. 
  Single repository turned out to be a time consuming mistake for me 
because when I decided to set up Trac (issue tracker with integration to 
SVN) I needed to split the projects out to their own repositories. 
Although this is possible in theory using "svnadmin dump" and 
svndumpfilter, in practice svndumpfilter is problematic to say the 
least.  Out of about 20 projects I only managed to dump and import about 
5 and they required extensive hand manipulation of the dump file.

The upshot of this is, in my opinion there is no reason to have a single 
repository with multiple projects.  If you have SVNParentPath in your 
apache config (assuming you are using http, not sure about SVNserve) all 
that needs to be done to set up a new project is "svnadmin create" and 
maybe add some access control to the AuthzSVNAccessFile.

Hope that helps...

Felix

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

Re: CVS to SVN Repository info

[Patrick Nelson <pn...@neatech.com>]

On Thu, 2004-07-08 at 02:07, Max Bowsher wrote:
> Do you mean the per-file revision numbers of files that are checked in?

Yes.

> I do not understand why this is the case. Please explain in exactly what way subversion's global revision number is not fulfilling
> your needs.

SVN uses the repos as the overall version change.  Like I said I don't
know what is the best way to do projects in SVN.  Is it to do a repos
for each project or group them?  If group them, then what would the
suggested structure be?  


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

Re: CVS to SVN Repository info

[Max Bowsher <ma...@ukf.net>]

Patrick Nelson wrote:
> FC1 SVN-1.0.5
>
> One of the things that we did with CVS was use the version tag that is
> issued with a check in.

"version tag that is issued with a check in"?

Do you mean the per-file revision numbers of files that are checked in?

>  This did an auto versioning for us that we
> liked and have gotten use to (MOC stuff here).  I understand that SVN
> does repos level versioning which I'm not sure how to do a best practice
> with.
...
> I've used the basic migration script:
>
>  cvs2svn.py -s <path2svnrepos>/sql <path2cvsrepos>/sql/
>
> and this creates the <path2repos>/sql with trunk, branches, and tags
> subdirs.  And then under each of these is the specific project subdirs.
> However, this removes any use of the SVN revision number like the CVS
> revision number could be used.

I do not understand why this is the case. Please explain in exactly what way subversion's global revision number is not fulfilling
your needs.

Max.


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