On Tue, Sep 9, 2008 at 16:05, G. T. Stresen-Reuter
> On Sep 9, 2008, at 8:28 PM, Hyrum K. Wright wrote:
>> G. T. Stresen-Reuter wrote:
>>> I'm working on a system that deploys the contents of repositories to
>>> development servers. I'll be using cURL to update the servers. I was
>>> hoping to use svn log --xml and XSLT to create the shell scripts
>>> required to update the servers, but I soon realized that the output of
>>> paths using svn log --xml does not appear to be in any order. svn log
>>> (without the --xml option) properly lists the order in which files need
>>> to be added/deleted, etc.
>>> This issue was reported in 2006 (but maybe not to the right place?)
>>> Unfortunately, there's no answer to that email (although it seems fairly
>>> clearly written).
>>> I'm wondering if anyone knows of a workaround, if this is a bug, or if
>>> the order simply doesn't matter (or if I'm just an idiot and missing
>>> something obvious).
>> Can you provide a specific example? Perhaps a reproduction recipe against
>> Subversion's own repository?
> Happy to oblige. Note that in the non-xml output, build.conf is the second
> line, but in the xml output, it is the fifth line. This becomes an issue for
> my specific project when updating directories: I can't add files to a
> directory that hasn't been created yet, so the A /trunk/my_directory has to
> come before A /trunk/my_directory/some_file.txt and that does not always
> seem to be the case (unless I'm missing something or just not paying
Given that the non-XML log output appears to be sorted alphabetically,
and the XML output appears to be unsorted, could you have your XSLT do
a sort on the child nodes of <paths>, thus achieving the same ordering
you get in the non-XML log?
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-09 22:28:12 CEST