* Florian Festi
On 01/03/2012 02:04 PM, Michael Schroeder wrote:
But did you look at the perl/python/ruby bindings? They provide a saner high level interface (at the cost of slowing things down, obviously). (Klaus Kaempf also wrote some glue code called "applayer", which offers a similar interface in C for the old sat-solver library. He used it for his bindings, I currently have the layer in the swig code.)
Yes, we had a look at the bindings (and examples). They are better than the pure C API but still expose many implementation details.
Well, it gives you all the capabilities and the flexibility of satsolver on the scripting language level. And there are quite some packages in openSUSE making use of it.
We'd rather not even expose the ids in the API but just the strings (or other tag data).
You can use the bindings in this way, while losing functionality. And a string is not sufficient to identify a package. So I wonder what level of detail you envision for the API ? Regards, Klaus --- SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org To contact the owner, e-mail: zypp-devel+owner@opensuse.org