From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Christopher Larson <clarson@kergoth.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: most efficient way to map perl RH rpms to OE package names?
Date: Tue, 25 Oct 2016 03:05:00 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1610250303460.20837@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.2.20.1610250246460.19688@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 2264 bytes --]
On Tue, 25 Oct 2016, Robert P. J. Day wrote:
> On Mon, 24 Oct 2016, Christopher Larson wrote:
>
> >
> > On Mon, Oct 24, 2016 at 1:53 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> > i've just been handed a list of about 200 perl packages by their
> > centos rpm names, and i want to map most, if not all, of them to their
> > equivalent OE package names.
> >
> > my first instinct (based on not having used a lot of perl OE
> > packages) is to add both "perl" and "perl-modules" to IMAGE_INSTALL,
> > just to fetch and build every possible module available through the OE
> > perl recipe -- that will at least give me an idea of what's available.
> >
> > next, i can see the pattern in some OE package names -- i've
> > verified that the Time::HiRes package is available in OE as
> > perl-module-time-hires, which i assume is part of the dynamic naming
> > being done in perl_5.22.1.bb.
> >
> > am i approaching this the right way?
> >
> >
> > Could also bitbake perl, then use oe-pkgdata-util to locate the
> > actual perl modules in the packages, i.e. */Time/HiRes.pm.
>
> i once wrote a wiki page on "bb", distinguishing between queries
> you could make before you did a build, versus queries that needed a
> build. it seems like oe-pkgdata-util needs a completed build for
> pretty much everything, do i have that right?
never mind, i just read this snippet from the YP ref manual:
"You can use the oe-pkgdata-util command-line utility to query
PKGDATA_DIR and display various package-related information. When you
use the utility, you must use it to view information on packages that
have already been built."
so i'm assuming that means for *all* oe-pkgdata subcommands, no
exceptions.
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================
next prev parent reply other threads:[~2016-10-25 7:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 20:53 most efficient way to map perl RH rpms to OE package names? Robert P. J. Day
2016-10-24 21:50 ` Christopher Larson
2016-10-25 6:42 ` Robert P. J. Day
2016-10-25 6:48 ` Robert P. J. Day
2016-10-25 7:05 ` Robert P. J. Day [this message]
2016-10-25 15:07 ` Christopher Larson
2016-10-26 3:20 ` Tim Orling
2016-10-26 9:48 ` Robert P. J. Day
2016-10-26 12:52 ` Robert P. J. Day
2016-10-26 9:55 ` Robert P. J. Day
2016-10-25 11:51 ` Robert P. J. Day
2016-10-25 12:11 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.20.1610250303460.20837@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=clarson@kergoth.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox