On Monday 24 February 2014 13:35:16 Martin Jansa wrote: > On Mon, Feb 24, 2014 at 12:19:07PM +0000, Paul Eggleton wrote: > > On Sunday 23 February 2014 22:26:34 Khem Raj wrote: > > > On Feb 23, 2014, at 10:23 PM, Lukas Bulwahn > > > <[email protected]>> > > > > wrote: > > > > We provide a recipe for python-netifaces in the meta-ros layer as > > > > well. In > > > > fact, a quick search on the OpenEmbedded Layer Index [1] reveals that > > > > meta-ros and meta-openstack both provide a recipe for > > > > python-netifaces. > > > > With your use case and recipe, we would have now three recipes. So, I > > > > suggest to unify all three recipes and come up with the best > > > > (complete) > > > > recipe from these three versions and add them to the meta-oe layer. We > > > > then can remove the duplicate recipes in the application layers. > > > > > > If these layers have dependency on meta-oe then please add the recipe > > > there > > > and remove from other places. > > > > There has been some discussion about creating a meta-python layer (within > > the meta-openembedded repository) for these kinds of recipes. I think the > > time has come to actually do that, before we add any further python > > recipes to the general meta-oe layer. Could someone send a patch to > > create meta-python? > I don't mind accepting patch for creating meta-python layer, but the main > reason for it (python-numpy, python-nose, python-mako) were already merged > into oe-core before this question was answered :/ > > http://lists.openembedded.org/pipermail/openembedded-core/2014-January/08808 > 9.html
Well, FWIW I have a few python recipes that could go there and I'm sure there will be others as well. Cheers, Paul -- Paul Eggleton Intel Open Source Technology Centre _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-devel
