RE: absolute paths in svn_wc_notify_t
From: Bert Huijben <bert_at_vmoo.com>
Date: Thu, 16 Oct 2008 11:09:39 +0200
The fix for this issue is in trunk. I noticed the same problem while
This method of using the path was unreliable before 1.5 as well L
It all depends on your current directory related to the commit location. The
In trunk/1.6 you will always receive an absolute path and optionally the
The lock functions have the same problem in 1.5 and where fixed in the same
From: Tom Naughton [mailto:naughtont_at_gmail.com]
I have an application that uses version 1.5.2 of the client library APIs.
Before 1.5, I relied on 'path' in svn_wc_notify_t to point to an absolute
Stepping through the subversion code I've been able to derive an algorithm
// Determine prefix stripped from the commit notify messages
const char *display_dir = "";
const char *base_dir = nil;
svn_depth_t depth = svn_depth_infinity;
err = svn_path_condense_targets(&base_dir, &rel_targets, commit_targets,
err = svn_path_get_absolute(&display_dir,display_dir, pool);
display_dir = svn_path_get_longest_ancestor(display_dir, base_dir,
If the current directory is something like "/Objects/Debug" and all of the
Is there a better way to figure out this prefix?
This is an archived mail posted to the Subversion Dev mailing list.