Re: Perl swig bindings starting to smell

Miller, Eric wrote:
> I disagree that the perl swig documentation has been updated, the trunk
> contains barely any updates to Client.pm from 1.4.2. Unless there is a
> patch not yet commited of course.

You are correct that Client.pm has had few changes; however Core.pm,
Ra.pm, Repos.pm, and Fs.pm are completely revised, to the point where
the lower-level bindings can be used by non-wizards (defined as anyone
not CLKao ;-).

I've written a short script to see what the latest tag for a project is,
see what trunk revision that was from, pull all of the log entries from
trunk that are newer than that, and present them to an editor (in
chronological order) for purposes of creating a commit message
summarizing the changes for a new tag. It's all part of my reworking of
Module::Release::SVK, to make managing my CPAN code more consistent and
simpler.

I'd also like to rewrite SVN::Notify to use the bindings if available
(instead of driving the commandline tools), so that my own subclasses
SVN::Notify::Mirror, ::Config, and ::Snapshot can all be faster and more
efficient.

> * I am unable to build the libsvn-perl shared library using the devel
> trunk for some reason so I had to hack on 1.4.2 code, else I would offer
> up a patch for my meager updates.

Send them to me and I'll work on getting them in shape to submit to the
list.

The Perl bindings need some higher level attention amongst the core
developers, but they are not by any stretch dead or all that stale...

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org