On Jan 3, 2005, at 11:47 AM, Max Bowsher wrote:
> I've looked over issue 1336.
> I think we can reasonably get relative externals working for 1.2, but,
> there is the question of how to format the relevant externals
> There are potentially *four* different kinds of relative externals (!):
> 1. Directory-relative externals.
> Straightforward, a path like "../../foo/bar" should DTRT.
> 2. Repository-relative externals.
> Conceptually straightforward (just use RA->get_repos_root()), but what
> syntax should they take? "/branches/foobar/mymodule"?
> But, should we also allow relative references to OTHER repositories?
> For example, currently in cvs2svn's repository, we have:
> Should this be specifyable using something like
> 3. Host-relative externals.
> Simple in concept, but what syntax to represent?
I would prefer to handle both 2 & 3 together. For example,
Would be used to compose an absolute URL by tacking the host and
repository access method onto the front of it. This wouldn't
discriminate between repositories on the same host, but instead merely
refer to a repository path that starts immediately after host:port/.
> 4. Scheme-relative externals.
> Consider a related grouping of repositories, maybe even on different
> hosts, which may be accessed either as http:// or https:// - but, if
> you are accessing one one way, you probably would rather use the same
> protocol for externals too.
> e.g. "myexternal httpsame://svn2.example.com/repos/beta/foo"
How about just dropping he repository access bit at the beginning? So
Received on Tue Jan 4 04:28:36 2005
- application/pkcs7-signature attachment: smime.p7s