[oe] [meta-python] README: contradictory indications?

[Derek Straka]

There are several recipes in meta-python that have dependencies in meta-oe:

gateone, python-dbus{mock}, python-pyzmq, python-snimpy

python-futures is also needed by a few recipes in meta-python.

I had thrown together a patchset a while to remove the dependency when
there was talk of splitting things out into separate repos, but I never
submitted it to the ML.

On Sun, Apr 29, 2018 at 11:22 AM, Khem Raj <raj.khem at gmail.com> wrote:

> On Sun, Apr 29, 2018 at 7:59 AM, Andrea Galbusera <gizero at gmail.com>
> wrote:
> > On Sat, Apr 28, 2018 at 10:03 PM, Khem Raj <raj.khem at gmail.com> wrote:
> >>
> >> On Thu, Apr 26, 2018 at 12:10 AM Andrea Galbusera <gizero at gmail.com>
> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I see that README in meta-python contains conflicting information
> >>> about layer's dependencies. The introductory paragraph states that
> >>> "modules in this layer need to be independent of openembedded-core and
> >>> meta-openembedded/meta-oe", then a few lines below both of these
> >>> layers are listed within meta-python's dependencies.
> >>>
> >>> To me, looks like the sentence in the introduction does not hold true
> >>> and can be removed. If you can help clarify what the correct
> >>> information is, I can send a patch to fix the documentation bits.
> >>
> >>
> >> Usually it shoudl be just core layer
> >
> > That's not the case, at least out of the box. Without meta-oe in
> > bblayers bitbake complains with:
> >
> > ERROR: Layer 'meta-python' depends on layer 'openembedded-layer', but
> > this layer is not enabled in your configuration
> >
> > Then, would be ok to drop 'openembedded-layer' from
> > LAYERDEPENDS_meta-python in conf/layer.conf? Parsing-wise it seems of
> > no hurt...
>
> I think if there is a dependency on meta-oe that could be beyond
> parsing e.g. compiling
> a recipe might assume another recipe from meta-oe during compile,
> ideally packageconfig
> for such features would be ideal. We can validate the dependencies via
> building each recipe
> from meta-python without meta-oe in layermix.
>
> It would be better to document whats actually happening in code even
> though it is less
> than ideal.
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>