[oe] DEPENDS += "module-build-perl-native" versus "libmodule-build-perl-native"?

[Robert P. J. Day]

  i'm sure i asked about this before, but i currently have a hacky
workaround in a build because of the mixture of DEPENDS mentioned in
the subject line.

  first, i've pulled down the meta-cpan layer, where you can see the
consistency of recipes that depend on a native build of the perl build
module:

$ grep -rh "DEPENDS.*module-build-perl-native" *
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
DEPENDS += "module-build-perl-native"
$

and, predictably, the meta-cpan layer provides that very recipe:

  module-build-perl_0.4216.bb

OTOH, the meta-openembedded/meta-perl layer takes a slightly
different approach:

$ grep -r "DEPENDS.*module-build-perl-native" *
recipes-perl/libhtml/libhtml-tree-perl_5.03.bb:DEPENDS += "libmodule-build-perl-native \
$

and provides the equivalent(?) recipe:

  libmodule-build-perl_0.31.bb

the last time i checked, trying to mix those two layers verbatim
generated a build error, since i include recipes which combine the two
dependencies, and try to install the identical content at the same
location. clearly(?), i should restrict the build-time dependencies to one or
the other of those recipes for the native perl build module.

  is this even considered an issue that should be resolved? it seems
that if layers are catalogued at the https://layers.openembedded.org/,
they should be compatible and play nicely together. in this case, it's
just a naming convention incompatibility -- as i recall, the OE naming
convention for perl modules is "lib....-perl", while the meta-cpan
does something different; hence, the problem.

  thoughts? should some names be cleaned up to prevent this?

rday

-- 

========================================================================
Robert P. J. Day                                 Ottawa, Ontario, CANADA
                        http://crashcourse.ca

Twitter:                                       http://twitter.com/rpjday
LinkedIn:                               http://ca.linkedin.com/in/rpjday
========================================================================