[meta-virtualization] meta-openstack Python support recipes

[Bruce Ashfield]

On Mon, Aug 11, 2014 at 12:17 PM, Paul Eggleton
<paul.eggleton at linux.intel.com> wrote:
> On Monday 11 August 2014 12:09:18 Bruce Ashfield wrote:
>> On Mon, Aug 11, 2014 at 8:43 AM, Paul Eggleton
>> <paul.eggleton at linux.intel.com> wrote:
>> > There are quite a few Python support recipes in meta-openstack. Now that
>> > the meta-python layer has been established, would it be reasonable to
>> > move those that are generic and not related to virtualisation over to
>> > meta-python and make meta-openstack depend upon that, so that those
>> > recipes can be (a little) more easily reused by others?
>>
>> At this point no. I intend to keep them all in meta-openstack, since the
>> version and cadence is tightly coupled to the core components, and
>> spreading them across multiple layers is a recipe for chaos.
>
> OK, understood - so I guess that being the case we may end up having some
> duplication between there and meta-python. Not that I intend to do any
> wholesale copying, but if we need a dependency or if it makes sense to add a
> recipe currently in meta-openstack to meta-python for the purposes of making
> it more widely usable, I don't see much of an option but to have it in both
> places.

Yep, and that's fine. Just drop an email if you do make a copy, and maybe some
can move. But generally speaking, openstack breaks in weird and wonderful
ways when dependencies change, so I can't be at the whim of another layer
updating and causing continual breakage.

At some point, there is such a thing as "over layerization", I've been down that
road before :)

Bruce

>
> Cheers,
> Paul
>
> --
>
> Paul Eggleton
> Intel Open Source Technology Centre



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"