One or multiple repositories?

[shoespeak]

Hello all,
Finally getting around to installing SVN on the server where I develop C programs. I came to this decision after reading about the different version control systems on another thread, and finding out that I've already got SVN installed.

I am setting it up and I can't decide if I should use multiple repositories for each project, or just one big one.

The projects are all pretty good size, but they are not worked on continuously...once one is finished, I don't really touch it again (they are mostly class projects at this point.) Because of this I was thinking about just setting up a new repository for each project inside the specific project folder.

How do other people use SVN?

(Sorry if this is a repeat of the other thread...if it is I will delete )

[Harkins]

I like one per project, and I'd think of a class as a project (because multiple assignments may use very similar code, or have you revising previous code).

[jannesiera]

I would create one repository and make subfolders for each project .

[Nox]

I would create one repository and make subfolders for each project .

I don't think that's a good idea, that way you'll have version numbers scatter around multiple projects etc. don't work with them much, maybe I'm wrong

On the other hand 1 repo per project is probably enough

[jannesiera]

I would create one repository and make subfolders for each project .

I don't think that's a good idea, that way you'll have version numbers scatter around multiple projects etc. don't work with them much, maybe I'm wrong

You are right, but I assume your project is stable when you finish it, so you won't have to go all the way back. Since it's only one project at the time and just for school it's easier to just create a subfolder.

[shoespeak]

Finally got SVN up and running...ugh what a pain that is when you know the bare essential linux commands!  Somehow I ended up creating empty SVN repositories in every directory...whoops!

Thanks for all the input.

I see online that this discussion is not new, and most people end up creating one big repository, with with subfolders as they are needed. I think when making these decisions you need to consider how many people will be using the repo and how active the projects will be.

[ninto]

None, use git

[dbest]

Git was a bit confusing for me to use.

[Harkins]

ninto: good answer, but you still have the question of one repo or many.

There's a couple nice free books on git available now: Pro Git (the best), Git Community Book (part of the official project), Git Magic (a bit rough, more of a collection of notes).

[ninto]

Sure thing, I'd say multiple, one per project.