SVN Versions

Question

Just a little SVN issue here.

I am setting up my own SVN server http://www.codinghorror.com/blog/archives/001093.html

Now I have made a reputation in which all my projects leave.

Now I checked the extract in the Projects folder.

Now, if I create a project and check it, this project is version 1. If I make a second project and check it, this project is in version 2. Thus, if I made changes to project 1, this project will be in version 3.

I would really like each project to have its own revision scheme. How can I do it?

Answer 1

You need to create repositories in the Projects folder, and when you do the initial check, select "??? / projects / repo1" ... this will keep working copies separately on your computer and you will enter / exit completely separate from each other friend.

Answer 2

The only way is for each project to be in a completely separate repository. Items in the same repository will always show the behavior indicated in your question.

From here

Unlike many other version control systems, Subversion revision numbers apply to all trees, not individual files. Each revision number selects a whole tree, a specific state of the repository after some fixed change.

Answer 3

You need to create a separate repository for each project. This is generally a good idea, so there is no shortage :)

Answer 4

Can you describe why having one revision number of a subtree in several projects is a problem for you?

There are some legitimate advantages to using a single repository for all of your projects. Most importantly, you are probably better able to control changes between shared code in multiple projects.

If you have a problem understanding one growing version of subversion in several projects, have you considered the situation when you introduce one of your projects? (remembering that the normal branch also has a globally increasing version number of the subversion)

Looks like you're trying to use the repository revision number as part of the build or release number? If possible, you could consider introducing a different assembly numbering scheme for your project / s, which could then be associated with the revision number of the subversion.

Such an association can be created using a branch agreement with the release number and posting a subversion revision in the comment for the branch.

Some schemes have been discussed in this matter.

Answer 5

They discuss this a little better: http://www.nabble.com/Multiple-Repositories-in-a-Windows-Server-td15014106.html

Basically you can:

svnserve -r /path/to/repository svn://hostname/ 

or

 svnserve -r /path/to/directory/containing/many/repositories svn://hostname/repositoryname/ 

Alternatively, you can go without a server and just place separate repositories on a local or network drive.