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: Wed, 26 Oct 2016 05:55:30 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1610260549570.17717@ca624034.mitel.com> (raw)
In-Reply-To: <CABcZANnku9xzQ=Zz6NnUX+myzbAX9K34gPVjkTCd0jKSAXSXRw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2237 bytes --]
On Tue, 25 Oct 2016, Christopher Larson wrote:
> On Tue, Oct 25, 2016 at 12:05 AM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
> On Tue, 25 Oct 2016, Robert P. J. Day wrote:
>
> > 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.
>
> Right, oe-pkgdata-util is about inspecting build output via pkgdata,
> whereas most of bb is inspection tools about the metadata — before
> the build. The only exception is bb-contents, which is a
> convenience, just wraps oe-pkgdata-util under the hood and tells the
> user the oe-pkgdata-util command in case they want to run it
> directly.
ah, excellent, this is important for me since, when i teach OE/YP,
one of the first things i do is distinguish between a "build" and
"nobuild" project directory ("nobuild" meaning configured only), and
use "bb" to show how much one can query about the project before any
compilation is done. this is amazingly useful.
rday
p.s. if readers don't know about "bb", i wrote a page on it once upon
a time:
http://www.crashcourse.ca/wiki/index.php/Bb
i better go back and make sure it's up to date.
--
========================================================================
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-26 9:56 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
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 [this message]
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.1610260549570.17717@ca624034.mitel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.