[OpenAFS] building swig based interfaces

Christof Hanke christof.hanke@rzg.mpg.de
Mon, 2 Sep 2013 14:23:47 +0200

Hi G=C3=A9mes,
On Sun, 01 Sep 2013 18:49:03 +0200
G=C3=A9mes G=C3=A9za <geza@kzsdabas.hu> wrote:

> Sorry if I wasn't clear with my intentions. I plan to have a python=20
> interface, where all the parts (volumes, pts entries, cache, etc) would=20
> be represented as objects. So basically I plan to have a few classes=20
> like volume, pts, cache, bos, with properties reflecting their state and=
> methods for manipulating them.
actually, the https://github.com/openafs-contrib/afspy
is doing that (and much more).
ATM, you don't see much activity on the master-branch, because
 I have created a new branch new_design
to get rid of issues I was seing while already using the=20
stuff on master branch.

Like Jakub, I think parsing the results of vos, fs commands is completely s=
The pathes to those binaries are not hardcoded, but can be changed quite=20
If you find something missing in afspy,
you are welcome to fill the gaps ;-)