You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Steve Folly <st...@blueyonder.co.uk> on 2005/11/09 00:05:36 UTC
svn:externals forces access protocol?
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
Re: svn:externals forces access protocol?
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Nov 9, 2005, at 05:58, Alan Ezust wrote:
> On 11/8/05, Ryan Schmidt <su...@ryandesign.com> wrote:
>
>> On Nov 9, 2005, at 04:33, Alan Ezust wrote:
>>
>>> I just discovered this today, and another annoying bit - if you
>>> do not
>>> specify the username for an URL, it assumes you are using the same
>>> username as that you are currently logged in as. Is there a way to
>>> specify a different username to be inserted into that URL?
>>
>> Don't you just use standard URL syntax for that?
>>
>> https://user@svn.example.com/foo/bar
>
> but where do you specify that? If you put it in the svn:externals
> property, then everyone who checks out the parent project needs to
> check out the child external project as the username specified in the
> svn:externals property. But typically, the desired username is
> specified once in the URL given in the svn co command line when the
> parent module is checked out.
Ah, you meant a different username *per user*. I don't know if that's
possible. I don't see a bug report about it....
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn:externals forces access protocol?
Posted by Alan Ezust <al...@gmail.com>.
but where do you specify that? If you put it in the svn:externals
property, then everyone who checks out the parent project needs to
check out the child external project as the username specified in the
svn:externals property. But typically, the desired username is
specified once in the URL given in the svn co command line when the
parent module is checked out.
On 11/8/05, Ryan Schmidt <su...@ryandesign.com> wrote:
>
> On Nov 9, 2005, at 04:33, Alan Ezust wrote:
>
> > On 11/8/05, Ryan Schmidt <su...@ryandesign.com> wrote:
> >
> >> Yes, this is a current limitation. Externals must be set using a
> >> fully-qualified URL including the protocol. The feature request to
> >> allow relative and absolute paths is here:
> >>
> >> http://subversion.tigris.org/issues/show_bug.cgi?id=1336
> >
> > I just discovered this today, and another annoying bit - if you do not
> > specify the username for an URL, it assumes you are using the same
> > username as that you are currently logged in as. Is there a way to
> > specify a different username to be inserted into that URL?
>
> Don't you just use standard URL syntax for that?
>
> https://user@svn.example.com/foo/bar
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn:externals forces access protocol?
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Nov 9, 2005, at 04:33, Alan Ezust wrote:
> On 11/8/05, Ryan Schmidt <su...@ryandesign.com> wrote:
>
>> Yes, this is a current limitation. Externals must be set using a
>> fully-qualified URL including the protocol. The feature request to
>> allow relative and absolute paths is here:
>>
>> http://subversion.tigris.org/issues/show_bug.cgi?id=1336
>
> I just discovered this today, and another annoying bit - if you do not
> specify the username for an URL, it assumes you are using the same
> username as that you are currently logged in as. Is there a way to
> specify a different username to be inserted into that URL?
Don't you just use standard URL syntax for that?
https://user@svn.example.com/foo/bar
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn:externals forces access protocol?
Posted by Alan Ezust <al...@gmail.com>.
I just discovered this today, and another annoying bit - if you do not
specify the username for an URL, it assumes you are using the same
username as that you are currently logged in as. Is there a way to
specify a different username to be inserted into that URL?
On 11/8/05, Ryan Schmidt <su...@ryandesign.com> wrote:
>
> On Nov 9, 2005, at 01:05, Steve Folly wrote:
>
> > 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?
>
>
> Yes, this is a current limitation. Externals must be set using a
> fully-qualified URL including the protocol. The feature request to
> allow relative and absolute paths is here:
>
> http://subversion.tigris.org/issues/show_bug.cgi?id=1336
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: svn:externals forces access protocol?
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Nov 9, 2005, at 01:05, Steve Folly wrote:
> 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?
Yes, this is a current limitation. Externals must be set using a
fully-qualified URL including the protocol. The feature request to
allow relative and absolute paths is here:
http://subversion.tigris.org/issues/show_bug.cgi?id=1336
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org