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

svn:externals forces access protocol?

From: Steve Folly <steve.folly_at_blueyonder.co.uk>
Date: 2005-11-09 01:05:36 CET

Hi,

By using svn:externals, would I be right in thinking I would then
forcing my users to use a specific protocol to access the repository?

I'm thinking of using the following layout. (Comments welcome...!)

        trunk/
                APP1/
                        src/
                        inc/
                        docs/
                APP2/
                        ...
                LIB1/
                        ...
                LIB2/
                        ...
                LIB3/
                        ...
                
        branches/
        tags/
        projects/
                PROJ1/
                PROJ2/

projects/PROJ1 would have the following svn:externals :

        APP1 svnserve://svn.example.com/trunk/APP1
        LIB1 svnserve://svn.example.com/trunk/LIB1
        LIB2 svnserve://svn.example.com/trunk/LIB2

projects/PROJ2 would have :

        APP1 svnserve://svn.example.com/trunk/APP1
        APP2 svnserve://svn.example.com/trunk/APP2
        LIB1 svnserve://svn.example.com/trunk/LIB1
        LIB2 svnserve://svn.example.com/trunk/LIB2
        LIB3 svnserve://svn.example.com/trunk/LIB3

The idea being that when a developer works on a particular project,
they just checkout projects/PROJ{1|2}, and they wont get the whole of
trunk/ (which, in real life includes *many* more projects and
libraries, plus some non-software stuff).

I appreciate the URL part can't be relative because that could get
messed up if I copy the directory somewhere else. However, I don't
*really* want to have to specify svnserve://svn.example.com/ on every
line. Just /trunk/APP1, /trunk/APP2, etc. would be nice, so that
whoever is doing the checkout will still be able to use whichever
protocol they initially used.

So with the prospect of all developers using the same protocol, if we
then decide to migrate from svnserve: to http: it means I'd have to
trudge through all those svn:externals and change them.

Is this just a current limitation, or am I missing something here?

BTW, I'm using Subversion 1.2.3 on Mac OS X 10.4.3. The repository is
a FSFS back-end if that helps.

Thanks for any help.

-- 
Regards,
Steve.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 9 01:07:30 2005

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.