You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Patrick Sunter <pa...@vpac.org> on 2004/03/24 22:29:40 UTC
RE: NEW FEATURE REQ: ability to specify/use aliases for repository
URLs
I strongly agree with Adam's idea below. And it would also allow svn:externals
to work when people are accessing the repository with different protocols.
Subversion is obviously storing the base URL of the current repository, so why
can't it allow these relative URLs?
seems to me it would produce a big improvement in usability. (And for not too
much coding effort?)
Adam Gibson wrote:
>> Probably too many issues with doing it this way and it was probably
>> ruled out already long ago since it seems such an easy way to do it to
>> me, but it would be very nice to just have the current url for the
>> project used for parent paths:
>>
>> Assuming structure in the repository is:
>> proj1|
>> |-trunk
>> |-tags
>>
>> svn co http://svnhost/svn/proj1/trunk svnproj1trunk
>>
>> cd svnproj1trunk
>>
>> svn cp ../trunk ../tags/proj1-1.0.2
>>
>> Let it use the existing url for the current project. If you need to
>> reference something differently than the current repository access
>> method then use the file:// or http:// method to specify.
>>
>> This subject should probably be moved to the dev list where I am sure
>> someone would be able to flank this idea pretty quickly
Patrick.
--
Patrick Sunter
--------------
Software Engineer
Victorian Partnership for Advanced Computing
E-Mail: patrick@vpac.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: NEW FEATURE REQ: ability to specify/use aliases for repository URLs
Posted by Benjamin Pflugmann <be...@pflugmann.de>.
Hi.
I don't mean to argue a
On Thu 2004-03-25 at 09:29:40 +1100, Patrick Sunter wrote:
> I strongly agree with Adam's idea below. And it would also allow
> svn:externals to work when people are accessing the repository with
> different protocols.
Interesting point.
The first use-case of aliases I have seen that cannot easily be solved
with shell variables. OTOH, there are other just as easy solutions, so
it's not a strict requirement. Aside from that remark, I don't intent
to argue about aliases per se.
> Subversion is obviously storing the base URL of the current repository, so
> why can't it allow these relative URLs?
What I meant to write about is just a side note: What Subversion
stores is not as obvious as you let it sound, considering that
Subversion doesn't store the base URL of the current repository
anywhere.
Subversion does store the base URL of the current directory in the WC
.svn area. To make the difference clearer: In the officical subversion
tree there exists (just an arbitrary example):
http://svn.collab.net/repos/svn/trunk/subversion/tests/clients/cmdline
What subversions currently stores in the WC is the complete URL. The
repository base URL would be:
http://svn.collab.net/repos/svn/
but there is no reliable way (without contacting the repository itself
and doing some queries) to find that out, especially considering the
possiblity to checkout only a sub-tree like
http://svn.collab.net/repos/svn/trunk/subversion/tests/
Regards,
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: NEW FEATURE REQ: ability to specify/use aliases for repository URLs
Posted by Ben Reser <be...@reser.org>.
On Thu, Mar 25, 2004 at 09:29:40AM +1100, Patrick Sunter wrote:
> I strongly agree with Adam's idea below. And it would also allow
> svn:externals to work when people are accessing the repository with
> different protocols.
>
> Subversion is obviously storing the base URL of the current repository, so
> why can't it allow these relative URLs?
>
> seems to me it would produce a big improvement in usability. (And for not
> too much coding effort?)
>
> Adam Gibson wrote:
> >> Probably too many issues with doing it this way and it was probably
> >> ruled out already long ago since it seems such an easy way to do it to
> >> me, but it would be very nice to just have the current url for the
> >> project used for parent paths:
> >>
> >> Assuming structure in the repository is:
> >> proj1|
> >> |-trunk
> >> |-tags
> >>
> >> svn co http://svnhost/svn/proj1/trunk svnproj1trunk
> >>
> >> cd svnproj1trunk
> >>
> >> svn cp ../trunk ../tags/proj1-1.0.2
> >>
> >> Let it use the existing url for the current project. If you need to
> >> reference something differently than the current repository access
> >> method then use the file:// or http:// method to specify.
> >>
> >> This subject should probably be moved to the dev list where I am sure
> >> someone would be able to flank this idea pretty quickly
Humm... My suggestion on the $SVNROOT thread might be a solution for
this problem as well:
http://www.contactor.se/~dast/svn/archive-2004-03/1106.shtml
--
Ben Reser <be...@reser.org>
http://ben.reser.org
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org