Re: [atomic-devel] Creating a new repo called libpod.

2017-11-01 Thread Clayton Coleman
I don't think we're ready to take advantage of shared libraries - they are still highly experimental and evolving, and I'd rather not be the tip of the spear on that. On Wed, Nov 1, 2017 at 11:44 AM, Daniel Walsh wrote: > On 11/01/2017 11:25 AM, Dusty Mabe wrote: > >> >> On 11/01/2017 11:17 AM,

Re: [atomic-devel] Creating a new repo called libpod.

2017-11-01 Thread Daniel Walsh
On 11/01/2017 11:25 AM, Dusty Mabe wrote: On 11/01/2017 11:17 AM, Daniel Walsh wrote: Basically we are looking to move kpod out of the kubernetes-incubator/cri-o project to allow it to grow on its own. We plan on building out the library for creating container pods to such an extent that CRI-O

Re: [atomic-devel] Creating a new repo called libpod.

2017-11-01 Thread Dusty Mabe
On 11/01/2017 11:34 AM, Antonio Murdaca wrote: > > > On Nov 1, 2017 16:26, "Dusty Mabe" > wrote: > > > > On 11/01/2017 11:17 AM, Daniel Walsh wrote: > > Basically we are looking to move kpod out of the > > kubernetes-incubator/cri-o project to allow i

Re: [atomic-devel] Creating a new repo called libpod.

2017-11-01 Thread Antonio Murdaca
On Nov 1, 2017 16:26, "Dusty Mabe" wrote: On 11/01/2017 11:17 AM, Daniel Walsh wrote: > Basically we are looking to move kpod out of the > kubernetes-incubator/cri-o project to allow it to grow on its own. We > plan on building out the library for creating container pods to such an > extent th

Re: [atomic-devel] Creating a new repo called libpod.

2017-11-01 Thread Dusty Mabe
On 11/01/2017 11:17 AM, Daniel Walsh wrote: > Basically we are looking to move kpod out of the > kubernetes-incubator/cri-o project to allow it to grow on its own. We > plan on building out the library for creating container pods to such an > extent that CRI-O could use it as well as kpod. >