[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: configure claims SWIG 1.3.29 < 1.3.24; huh?

From: B. Smith-Mannschott <benpsm_at_gmail.com>
Date: 2006-05-03 10:41:58 CEST

* Subversion+python API support builds successfully with SWIG 1.3.25.
(Though the misleading warning message still needs fixing.)

* I also found that I had to manually add /usr/local/lib/svn-python to
my PYTHONPATH before things would actually work. Well by "work", I
mean I can import the svn.* modules. I haven't actually tried to call
any of the APIs (see next point)

* At this point, I encountered my next problem. The Subversion API
(for python) is: (1) huge and (2) undocumented. I've since generated
the docs for the C API using doxygen as I gather that they parallel
the SWIG APIs closely.

As much as the "well defined API" is a selling point of Subversion
(over CVS), I'm inclinded to think that scriptability is better served
by supporting it explicitly in the CLI tools. (And this is just what
the --xml switch many svn commands now support does. Hurrah!)

(parenthetically: is there some externalized (XML) representation for
the changes applied by a merge operation? A sort of
diff+properties+directory operations?)

// ben -- occs'97
Received on Wed May 3 10:43:09 2006

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.