On Wed, Aug 19, 2015 at 8:18 AM, Zygmunt Krynicki <
<email address hidden>> wrote:
> Hey.
>
> Sorry, I'm just wrapping my head around this. I think it should _not_
> depend on python 3. A provider is just a collection of definitions. We need
> python and plainbox on the build machine but the target machine does not
> need python (plainbox is a framework).
Sorry (me too ;-) ), but I have to ask. What is the reasoning for the
plainbox runtime to be a framework?
Can't snapcraft just bundle it all together into one harmonious app snap?
Do you see any potential in keeping them separate at all?
On Wed, Aug 19, 2015 at 8:18 AM, Zygmunt Krynicki <
<email address hidden>> wrote:
> Hey.
>
> Sorry, I'm just wrapping my head around this. I think it should _not_
> depend on python 3. A provider is just a collection of definitions. We need
> python and plainbox on the build machine but the target machine does not
> need python (plainbox is a framework).
Sorry (me too ;-) ), but I have to ask. What is the reasoning for the
plainbox runtime to be a framework?
Can't snapcraft just bundle it all together into one harmonious app snap?
Do you see any potential in keeping them separate at all?