On Mon, 13 Nov 2017 19:03:07 +0100, Stefan Sperling <stsp_at_elego.de>
wrote:
>
>Subversion stores access permissions in a special configuration file
>on the server, so you'll have to re-create users, groups, and their
>access rights in the SVN server's configuration:
>http://svnbook.red-bean.com/nightly/en/svn.serverconfig.pathbasedauthz.html
>
Thanks I will look into that more closely.
One question, though, that might be a terminology misunderstanding on
my part:
In CVS a repository is the container for a lot of different "modules",
which are top level directories below the root of the repository (or
else defined in CVSROOT/modules).
When reading your link above I found I became hesitant as to what SVN
means by "repository", it does not look like it is a 1-1 compared to
CVS...
I have as I said 6 CVS repositories served by CVSNT in order to
isolate files that are to be kept separate. For example the hardware
designers use repo HW for their firmware developments, Windows
application developers use repository PC and marketing uses Marketing
for their documents etc.
So in essence I have 6 different repositories in CVS language.
How does this map into SVN?
The SVN path-based authorization seems to be dealing with repositories
(modules?) within the repository (singular), all below the SVN root...
Did I misunderstand the way SVN works?
--
Bo Berglund
Developer in Sweden
Received on 2017-11-13 20:11:27 CET