Re: xml output changed - relative paths now appearing?

[CC to dev]

Alexander Haley <ahaley_at_meditech.com> writes:

> On Mon, Jul 15, 2013 at 5:21 PM, Philip Martin
> <philip.martin_at_wandisco.com>wrote:
>
>> I could not get this to happen on Linux. Are you using the same path in
>> the checkout and status commands? Can you provide a complete recipe?
>> Something to do with drive letters, or case differences perhaps?
>>
>
> I am using WindowsXP - the svn binaries came from TortoiseSVN. I've
> attached the batch file script which can reproduce this, as well as
> transcripts from a machine with svn 1.7.x and another with 1.8.0 for
> comparison. My reported snag is the 6th line of the XML output, where the
> two differing results are:
>
> 1.7.x path="C:\testing\bug-test">
> 1.8.0 path="..\..\..\bug-test">

svnadmin create repo
svn co file://`pwd`/repo wc
svn mkdir wc/foo
AbsWC=`pwd`/wc
cd wc/foo
svn st --xml $AbsWC

With 1.7 I get

<target
   path="/home/pm/sw/subversion/obj/wc">
<entry
   path="/home/pm/sw/subversion/obj/wc/foo">

while with 1.8 I get

<target
   path="/home/pm/sw/subversion/obj/wc">
<entry
   path=".">

The entry for 'foo' can only be identified by interpreting the path
relative to the current directory, information that is not part of the
XML. That feels wrong to me.

If I use a relative path "svn st --xml .." then 1.8 gives what looks
more useable output:

<target
   path="..">
<entry
   path="../foo">

The non-XML output shows the same paths, I suppose it makes more sense
but the difference between absolute and relative paths remains:

svn st $AbsWC
A

and

svn st ..
A ../foo

Which output form do we want? Perhaps we should be printing paths
relative to the target rather than the current working directory?

-- 
Philip Martin | Subversion Committer
WANdisco | Non-Stop Data
www.wandisco.com