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

Re: Additional parameter for svn to list directoriy with multiple/parallel/differents repositories

From: Omar Martin Medina Izaguirre <omar.medina_at_web.de>
Date: Thu, 05 Jun 2008 13:15:13 +0200

Hello John,

Sorry, but i am not agreed with your oppinion.
your disagreement does nor go with the currently implemented SVNserve-functionalities. let me explain

FIRST:
1.- i am talking about "access to remote repositorie and svnserve is used"
2.- svn -listrepositories can only work together with svnserve (bad suggestion)
3.- please forget APACHE: SVNserve and Apache are two differents products
4.- Apache can not be used in my work-place, the reasons are already known
6.- i am talking about global/common repositories, not user/repository specific
7.- FACT is now: using SVNserve it is possible to have access to different repositories, even if "Each Subversion repository is complete unto itself"
    BUT here the user needs to address/give the right path. that is what we are using now.
    ----------------------
    on SVNserve/Repository PC we have following structure (xxx.xxx.xxx.xxx port:3096)
    /abc/repos/repo1
    /abc/repos/repo2
    /abc/repos/repo3
    .....
    /abc/repos/repoX
    ----------------------
    on SVNserve/Repository PC is running the svnserve with following argument
    svnserve -d -r /abc/repos
    ----------------------
    on the client/USER PC we call svn with following command, and it works
    svn co svn://xxx.xxx.xxx.xxx.30.96/repo1
    or
    svn co svn://xxx.xxx.xxx.xxx.30.96/repoX
    the problem here, the USER need to kwon, the repository name.
    That means: SVNserver have access to the different repositories without problems

8.- Why dou you need a glogal list or register of repositories.
svnserve knows the parent directory (svnserve -d -r /abc/repos). where ist the problem, that SVNserver seeks for repository names
and in the svnserve.conf for a new entry is "list= public" //or private" (list is a new feature)

/abc/repos/repo1/conf/svnserve.conf (new entry list = public or private , default private)

Your argument "private repositories can bee seen" will be not more valid.

SUGGESTION:
2. suggestions

1.- svn -listrepositories svn://xxx.xxx.xxx.xxx.30.96
list all public directories specified in the root-directory of SVNSERVE

2. new entry in conf\svnserve.conf
to manage the access
for example list, it can have two values,
#the repository name is public
list=public

#the repository name is public
list=private

best reagard

-- 
--------------------------
Omar Martin Medina Izaguirre
Dörner Str. 42
51674 Wiehl
Tel. +49-2262-712250
--------------------------
______________________________________________________________
Jeden Monat 1 hochkarätiger maxdome-Blockbuster GRATIS!
Exklusiv für alle WEB.DE Nutzer. http://www.blockbuster.web.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-06-05 17:32:02 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.