From: "Mikko Rapeli" <mikko.rapeli@bmw.de>
To: <cJ-yocto@zougloub.eu>
Cc: <mikko.murto@hhpartners.fi>, <yocto@lists.yoctoproject.org>,
<licensing@lists.yoctoproject.org>
Subject: Re: [licensing] [yocto] Package names in IMAGE_MANIFEST and PACKAGES
Date: Fri, 26 Feb 2021 15:21:10 +0000 [thread overview]
Message-ID: <YDkR5bUm7W9qCSyg@korppu> (raw)
In-Reply-To: <20210226100914.33f5684c@pouet.cJ>
Hi,
On Fri, Feb 26, 2021 at 10:08:47AM -0500, Jérôme Carretero wrote:
> On Fri, 26 Feb 2021 14:18:59 +0000
> "Mikko Murto" <mikko.murto@hhpartners.fi> wrote:
>
> > The crux of the matter is that I need to find packages created by recipes and to link the packages listed in image's manifest files to these packages.
>
> The way I've been doing it, which is probably not optimal and specific
> to one package format, is to lookup .ipk packages from the image
> manifest, then use the .ipk control info "OE" key to find the
> originating recipe.
FWIW, the mapping from binary package names recipes and recipe metadata like
LICENSE is available from buildhistory. Also binary package content of images
is available from buildhistory. With some scripting it is possible to list
recipes which produce binaries to images, except for static linking and
header-only recipes but I hope these cought via some other way.
Cheers,
-Mikko
next prev parent reply other threads:[~2021-02-26 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-26 14:18 Package names in IMAGE_MANIFEST and PACKAGES mikko.murto
2021-02-26 15:08 ` [yocto] " Jérôme Carretero
2021-02-26 15:21 ` Mikko Rapeli [this message]
2021-02-26 16:01 ` [licensing] " Jérôme Carretero
2021-02-26 15:45 ` Richard Purdie
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=YDkR5bUm7W9qCSyg@korppu \
--to=mikko.rapeli@bmw.de \
--cc=cJ-yocto@zougloub.eu \
--cc=licensing@lists.yoctoproject.org \
--cc=mikko.murto@hhpartners.fi \
--cc=yocto@lists.yoctoproject.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.