Daniel Shahaf wrote on Tue, Apr 24, 2012 at 01:34:16 +0300:
> (Obligatory invitation for you to want to write a patch that exposes
> svn_wc_status_func2_t to the Perl bindings goes here.)
And thanks, etc. I'm just a bit too tired for the full boilerplate
right now :-/
>
> http://subversion.apac
(Obligatory invitation for you to want to write a patch that exposes
svn_wc_status_func2_t to the Perl bindings goes here.)
http://subversion.apache.org/patches
Jim Searle wrote on Mon, Apr 23, 2012 at 11:42:33 -0700:
> Thanks. Yes, it does look like svn_wc_status_func_t is ifdef'ed out
> for pe
Thanks. Yes, it does look like svn_wc_status_func_t is ifdef'ed out
for perl bindings. So, I assumed it was an issue with the perl
bindings, and reported it to Alien-SVN, but I was told it needs to be
reported to subversion.
I tried to find if this is a known issue, but can not seem to find
one.
Hmm. A quick glance at subversion/bindings/swig/svn_wc.i tells me that
perhaps svn_wc_status_func2_t aren't supported by the Perl bindings?
(notice the pattern of #ifndef's around svn_wc_status_func_t and
svn_wc_status_func2_t)
Jim Searle wrote on Fri, Apr 20, 2012 at 14:21:52 -0700:
> I was able
I was able to get info2 working with Daniel's suggestion, but now I
can not get status3 to work.
For the code below I get this error when it tries to run status3:
TypeError in method 'svn_client_status3', argument 4 of type
'svn_wc_status_func2_t'
Seems like it wants me to typecast the subroutine
Jim Searle wrote on Wed, Mar 21, 2012 at 16:03:05 -0700:
> I am currently using the perl api info and diff_summarize methods, but
> I need to switch to info2 and diff_summarize2 since they support the
> 'depth' option. But I can't figure out the correct syntax, does
> anyone have an example?
>
%
I am currently using the perl api info and diff_summarize methods, but
I need to switch to info2 and diff_summarize2 since they support the
'depth' option. But I can't figure out the correct syntax, does
anyone have an example?
Thanks,
Jim
