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

Re: Several projects in one repository?

From: Simon Large <simon.tortoisesvn_at_gmail.com>
Date: Wed, 20 May 2015 09:56:33 +0100

On 19 May 2015 at 17:22, H Nalen <david.goliat0_at_gmail.com> wrote:

> Hi,
> I'm really beginner with this revision manager. I perhaps even use wrong
> words or perhaps I posting in wrong community..so, please be patient.
>

As Justin already mentioned, plese use the users list instead of the dev
list.

I have used VSS earlier in several sw-projects but I must use a better tool
> to handle the revisions. Now I testing TortoiseSVN.
>
> My question.
> Can I have one big repository for many small sw-projects or should I
> create several repositories, one for each customer we have?
>
>
Again as Justin said, you can do either. THere are a couple of things which
would influence your decision:
1. You can copy files and directories within a repository, so if you have
similar projects you can copy the code and still see its original history.
You can't do that across different repositories.

2. If you are writing code for different customers and you are likely to
want to split that off so you can give them access to only their code, or
maybe sell the intellectual property then it is easier to use separate
repositories. It is possible to split a repository later on but it can be a
lot of work if there are copies between different (unrelated) projects.

> The sw-projects sometimes sharing code, perhaps some few display routines.
>
> The filetypes in each project is mix of txt and bin.
> (Code for Atmel processors, written in Ansi-C using Atmel Studio)
>

What are the binary files you need to put into the repository? Normally you
would only version source files and project files (XML in Atmel Studio).
Object files and other intermediates are best excluded from the repository
as they can be regenerated from the source, they take up a lot of space in
the repository and they make it hard to see what has changed. I had a
colleague do that once; for every commit there were 100 object files
(changed because of because of internal timestamps) and one source file
which may have had a 1 line change.

Of course if you are using Word documents or similar then they are binary
and you don't have a lot of choice.

Hmm....if we sharing code and/or some other documents we must have the
> projects in the same repository?
>
>

There are several ways of sharing code.
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-howto-common-projects.html

Simon

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3118288

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-05-20 10:56:58 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.