<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Oct 24, 2016 at 1:53 PM, Robert P. J. Day <span dir="ltr"><<a href="mailto:rpjday@crashcourse.ca" target="_blank">rpjday@crashcourse.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":2hk" class="a3s aXjCH m157f88e7b04000e9"> i've just been handed a list of about 200 perl packages by their<br>
centos rpm names, and i want to map most, if not all, of them to their<br>
equivalent OE package names.<br>
<br>
my first instinct (based on not having used a lot of perl OE<br>
packages) is to add both "perl" and "perl-modules" to IMAGE_INSTALL,<br>
just to fetch and build every possible module available through the OE<br>
perl recipe -- that will at least give me an idea of what's available.<br>
<br>
next, i can see the pattern in some OE package names -- i've<br>
verified that the Time::HiRes package is available in OE as<br>
perl-module-time-hires, which i assume is part of the dynamic naming<br>
being done in <a href="http://perl_5.22.1.bb" rel="noreferrer" target="_blank">perl_5.22.1.bb</a>.<br>
<br>
am i approaching this the right way?</div></blockquote></div><br>Could also bitbake perl, then use oe-pkgdata-util to locate the actual perl modules in the packages, i.e. */Time/HiRes.pm.<br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Christopher Larson<br>clarson at kergoth dot com<br>Founder - BitBake, OpenEmbedded, OpenZaurus<br>Maintainer - Tslib<br>Senior Software Engineer, Mentor Graphics</div>
</div></div>