On Tue, 14 May 2013 14:13:45 -0500 Serge Hallyn <serge.hal...@ubuntu.com> wrote:
> Hi, > > I'd like to rewrite lxc-create to be c (calling out to the c templates > which continue to be scripts for the most part). Unfortunately right > now the lxcapi_create() just takes arguments to send to the lxc-create > script. > > I could either dump the existing lxcapi_create function, replace it > with something close to the lxcapi_clone, and update the current > callers, or I can write a new function lxcapi_create2, keeping > lxcapi_create() as calling the c program (which then calls > lxcapi_create2 :). > > The only reason to go with lxcapi_create2 would be for out of tree > callers (which includes the go bindings). Since we're not at 1.0 yet > we don't guarantee anything about api stability (for exactly this > reason), but I thought I'd ask anyway what you all thought. I'd vote for trying to keep the API as clean as possible until 1.0, but then I don't have an out of tree caller to update. This brings up a question though, with 1.0 we are going to consider stable the lxcapi_* routines only and not all symbols available from liblxc.so, correct? > -serge ------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
