Re: most efficient way to map perl RH rpms to OE package names?

["Robert P. J. Day" <rpjday@crashcourse.ca>]

  following up on my original query, i'm now in the process of
"mapping" a couple hundred CentOS perl rpms to their OE equivalents,
and here's the process so far; just want to check that i'm going about
this in a sane way.

  first, as chris larson suggested, use "oe-pkgdata-util" to see which
generated perl modules appear to match up to equivalent rpms, and
quite a number of them seem to be direct equivalents, such as:

 * perl-HTTP-Tiny-0.033-3.el7.noarch
 * perl-module-http-tiny

so examples like that appear pretty straightforward.

  next, i noticed that there are a few perl recipes under OE,
recipes-devtools and recipes-extended, a couple *apparent*
equivalents:

 * perl-XML-LibXML-2.0018-5.el7.x86_64
 * libxml-perl_0.08.bb

 * perl-XML-NamespaceSupport-1.11-10.el7.noarch
 * libxml-namespacesupport-perl_1.11.bb

and so on. not so many of those but still, that took care of a few
more matches.

  finally, i figure i'm going to have to dive into meta-cpan for the
rest, and here's something puzzling.

  one of the RH rpms to be matched was
perl-IO-Compress-2.061-2.el7.noarch, but the generated modules were:

  perl-module-io-compress-deflate
  perl-module-io-compress-adapter-bzip2
  perl-module-io-compress-zlib-extra
  perl-module-io-compress-zip-constants
  perl-module-io-compress-bzip2
  perl-module-io-compress-adapter-identity
  perl-module-io-compress-zlib-constants
  perl-module-io-compress-base-common
  perl-module-io-compress-adapter-deflate
  perl-module-io-compress-gzip
  perl-module-io-compress-zip
  perl-module-io-compress-gzip-constants
  perl-module-io-compress-base
  perl-module-io-compress-rawdeflate

but no "perl-module-io-compress", which is what i would have expected.

  however, if i pop over to meta-cpan, there *is* a recipe file
"io-compress-perl_2.069.bb". can anyone explain how i should interpret
this?

  it seems (and i am not a perl expert) that the foundation
IO::Compress recipe is at meta-cpan, but the more specific sub-modules
are built from the base OE perl recipe. or is it that these modules:

  perl-module-io-compress-base-common
  perl-module-io-compress-base

represent the base class? i'm just trying to figure out the standard
OE packaging for perl modules.

rday

-- 

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

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