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

RE: svn_client_status and path relativity

From: Bert Huijben <rhuijben_at_sharpsvn.net>
Date: Mon, 12 Oct 2009 09:48:59 +0200

> -----Original Message-----
> From: Branko ─îibej [mailto:brane_at_xbc.nu]
> Sent: maandag 12 oktober 2009 2:21
> To: Bert Huijben
> Cc: 'Roman Donchenko'; dev_at_subversion.tigris.org
> Subject: Re: svn_client_status and path relativity
> Bert Huijben wrote:
> > (One major issue is that there are an
> > infinite numbers to describe a path in relative form. Luckily there
> is just
> > one absolute path)
> >
> Do we make certain of that? What about symlinks in the path?

That is a completely different layer of abstraction.

There is an infinite number of relative paths that describe an absolute path. (That is what I was trying to describe here, because that is what we changed).

There is also an infinite number of paths that can describe a different target. (symlinks, hardlinks, mounts, ..., ...). But this is handled at the io and working copy level. (In some cases we want to version the symlinks, but in some cases we want to ignore them)

We have a major issue with relative path forms in the old access baton based api.. You can have multiple access batons with a different path describing and caching the same path in different ways. Those issues are mostly resolved by always using absolute path internally.
(E.g. it allows using hashtables on paths).

Handling other things becomes a lot easier if we remove a few other problems that have hardcoded workarounds all through our internal api.


Received on 2009-10-12 09:49:19 CEST

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.