ZYpp API is a toolkit. It provides not only the package management API but all the classes and components like a LEGO set. In this regard, its goals as an API are very similar to LLVM. This makes the API complex to wrap in scripting languages, both technically and from the user point of view: the wrapped API does not make much sense for simple tasks. However, we have seen the need for a simple client API that encapsulates all the knowledge there. Ideally this would be a simple API, comparable to what zypper offers, or what PackageKit offers. This API could actually be used by zypper and the PackageKit backend, which would serve as a good testbed for its usefulness. The API could be done in plain C, exposing only opaque structs keeping the ZYpp data and some API to do operations, but avoiding exposing other types that would conflict with scripting languages own stdlibs (Pathname, Date, etc), so restricting itself to basic types only. Having a simple C API would allow for easy binding: you can use swig, ffi, interpreter own API, etc. If we follow conventions like class_methodname(class *, args).. etc bindings get easier... Now, how this API would look like? Lets collect use cases. Where possible I would prefer actual client code examples in C, python, etc together with the use case (only usecases could lead to a committee-taste API). -- Duncan Mac-Vicar P. - http://www.suse.com/ 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 For additional commands, e-mail: zypp-devel+help@opensuse.org