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 <ben@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
Received on Thu Apr 1 23:07:25 2004