From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Giuseppe Condorelli <giuseppe.condorelli@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: How to query installed rpm packages
Date: Mon, 28 May 2012 17:23:55 +0100 [thread overview]
Message-ID: <3418839.G4f3PdLdKK@helios> (raw)
In-Reply-To: <CAOHjBZsnd8aZjp5ZAvPZ2p3R9AmxGoLXZhVMQjOJxS8Bto61BA@mail.gmail.com>
On Monday 28 May 2012 17:30:34 Giuseppe Condorelli wrote:
> Well, I added ROOTFS_POSTPROCESS_COMMAND += "list_installed_packages ; " in
> the image recipe I want to build.
> Build went right but I don't know where to find the output the
> list_installed_packages has provided.
> Any suggestion? Am I wrong?
All list_installed_packages does is print a list of the packages; if you just
add it to ROOTFS_POSTPROCESS_COMMAND the output will be going into the log file
for the image task which is probably not what you want. If you wanted to
proceed with this I think you'd need to redirect the output to some file
somewhere - this is easily done by instead calling your own shell function and
then calling list_installed_packages > path/to/some_output_file.txt within it.
However it sounds like buildhistory will do what you want here anyway.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-05-28 16:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 13:14 How to query installed rpm packages Giuseppe Condorelli
2012-05-28 13:26 ` Paul Eggleton
2012-05-28 15:30 ` Giuseppe Condorelli
2012-05-28 16:23 ` Paul Eggleton [this message]
2012-05-29 13:20 ` Giuseppe Condorelli
2012-05-29 13:32 ` Paul Eggleton
2012-05-29 13:49 ` Giuseppe Condorelli
2012-05-30 10:29 ` Giuseppe Condorelli
2012-05-30 10:34 ` Paul Eggleton
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=3418839.G4f3PdLdKK@helios \
--to=paul.eggleton@linux.intel.com \
--cc=giuseppe.condorelli@gmail.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.