On 06/21/2012 11:37 AM, Diego Elio Pettenò wrote:
> Il 09/06/2012 19:36, Stéphane Graber ha scritto:
>> Yes, the new version of liblxc will be public and will have proper ABI
>> versioning (as should be expected from any public library).
>
> Since you're working on the Python packages, is there an
Il 09/06/2012 19:36, Stéphane Graber ha scritto:
> Yes, the new version of liblxc will be public and will have proper ABI
> versioning (as should be expected from any public library).
Since you're working on the Python packages, is there any chance you
could get my libtoolization patch in?
If you
Il 07/06/2012 23:57, Serge Hallyn ha scritto:
> we've been talking (including a session at UDS) about getting a nice
> API out of liblxc, with exports to python etc
If you want to do that please make it ABI stable, as right now it isn't.
I've already sent patches to make the library build happenin
On 06/09/2012 01:29 PM, Diego Elio Pettenò wrote:
> Il 07/06/2012 23:57, Serge Hallyn ha scritto:
>> we've been talking (including a session at UDS) about getting a nice
>> API out of liblxc, with exports to python etc
>
> If you want to do that please make it ABI stable, as right now it isn't.
>
Absolutely, especially the Python bit! I wrote a psuedo-OO wrapper
for OpenVZ (basically makes a bunch of vzctl calls at a higher layer
of abstraction so you can/start/stop/configure large numbers of
containers) and was thinking about writing something similar for LXC
that called the lxc-* BUT alw
Hi,
we've been talking (including a session at UDS) about getting a nice
API out of liblxc, with exports to python etc. This could be used: to
easily replace some of the tools which are currently scripts; to
increase code sharing with other projects - most immediately arkose and
libvirt; and to
