[cvsnt] max number of repositories?

[IVO.HECHMANN at SBB.CH]

--- Erhalten von  I0.U114371 0512 20 26 41                   12.11.03 10.14

hai bo, thanks for your answer;

the reason is that i think the effort to define user privileges using NTFS
security is too high; we habe about 100 developers and some extern
collaborators. defining their privileges using NTFS means that each project
admin has to waste around with the privileges on the server's filesystem.

worst case: in one year, EVERYONE has ALL rights EVERYWHERE. many users will
have privileges but the users have left the company long time ago...

the privileges are not created to keep code hidden, its done to prevent
unwanted changes (we use PVCS at the moment which follows the pessimistic
locking system...).

using a repository per project allows the project admin to add a writers
file, which is much easier to handle than NTFSprivileges;

best thing would be a writers file per MODULE, not per repository, but i
know thats not possible...

anyway your answer helped me alot.

regards

ivo
(i know, my english is bad, but my taylor is rich...)




****************************************************************************


From: bo.berglund at telia.com
To: cvsnt at cvsnt.org
Date: Tue, 11 Nov 2003 19:27:18 +0100
Subject: Re: [cvsnt] max number of repositories?

On Tue, 11 Nov 2003 13:25 +0100, IVO.HECHMANN at SBB.CH wrote:

>--- Erhalten von  I0.U114371 0512 20 26 41                   11.11.03 13.25
>
>hai all;
>
>i've just successfully installed CVSNT and now i found an old message at
>http://www.cvsnt.org/pipermail/cvsnt/2002-May/002138.html which says that
>cvsnt may handle only <=64 repositories; well i was shocked, but when i
>added 70 repositories for testing it worked fine. i am using cvsnt
>v.2.0.0.9, is this an old limitation which has been removed?
>

The limit has been moved up to some high value that I don't know.
But why in the world do you want to have so many repositories???
I think that you might have misunderstood the workings of CVS here.
You don't need a *repository* for each project you want to maintain,
instead you create a *module* for each. The only reason I can think of
to separate stuff into different repositories is when you want to make
sure there can be no interaction between the modules of each. This can
happen for example if you work on a consultancy basis and you want to
keep customer code well isolated.

However, dividing stuff into different respositories makes it
impossible to use the built-in cvs support for creation of logical
modules where some support files are part of many different projects.
This cannot be done across repositories.


/Bo
(Bo Berglund, developer in Sweden)
_______________________________________________
cvsnt mailing list
cvsnt at cvsnt.org
http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt

---- 12.11.03 10.14 ---- Gesendet an   -------------------------------------
  -> cvsnt at cvsnt.org