Mailinglist Archive: yast-devel (85 mails)

["Duncan Mac-Vicar P." <dmacvicar@xxxxxxx>]

On Wednesday 25 July 2007 09:20:24 am Klaus Kaempf wrote:
> * Duncan Mac-Vicar P. <dmacvicar@xxxxxxx> [Jul 25. 2007 00:17]:
> > Hi people
> >
> > I want to merge some changes I have in my machine to the ruby bindings,
> > so I thought about moving them to trunk first.
>
> The old, hand-crafted bindings or the new swig-based ones ?

UHm, I am talking about YaST, not ZYpp.

YaST ruby bindings are handcrafted as it is only a plugin which adds support 
for loading .rb modules, importing the ruby symbols in ycp, do ycp rb type 
convertion and namespace/function/component invocation. They don't wrap APIs.

The other part is a ruby module which does the same as above, but in the other 
direction. It defines a ruby module which acts as a dynamic proxy which 
allows to invoke YaST symbols.

The third part, are ruby swig bindings for the yast libraries, but I have no 
usecase for them and I think they are disabled for compiling, unless you want 
to write a static checker or a yast compiler in ruby you don't need this 
part.

> > any objections?
> > only one thing: they build with cmake
> >
> > Does it make sense to have a directory ruby-bindings and then
> > python-bindings, or do we create a bindings directory and put them all
> > there, including the perl ones?
>
> Whats their respective size ?

I don't know about the python ones, perhaps somebody from Prag could hint me?

Ruby ones are 124k + config

duncan@piscolita:/space/git/suse/yast2-ruby-bindings.new> du -c --exclude=.git
8       ./modules
8       ./cmake/modules
12      ./cmake
4       ./package
36      ./examples/ruby
40      ./examples
100     ./src/ruby
16      ./src/swig
124     ./src
216     .
216     total
-- 
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx