From: "Jérôme Carretero" <cJ-yocto@zougloub.eu>
To: "Mikko Rapeli" <mikko.rapeli@bmw.de>, <mikko.murto@hhpartners.fi>
Cc: <yocto@lists.yoctoproject.org>, <licensing@lists.yoctoproject.org>
Subject: Re: [licensing] [yocto] Package names in IMAGE_MANIFEST and PACKAGES
Date: Fri, 26 Feb 2021 11:01:31 -0500 [thread overview]
Message-ID: <20210226110158.6366efdb@pouet.cJ> (raw)
In-Reply-To: <YDkR5bUm7W9qCSyg@korppu>
[-- Attachment #1: Type: text/plain, Size: 1034 bytes --]
On Fri, 26 Feb 2021 15:21:10 +0000
"Mikko Rapeli" <mikko.rapeli@bmw.de> wrote:
> 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.
Definitely more powerful than just image manifest + packages.
> 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.
Yeah, that "except" part is something that should be accounted for.
The thing is, I don't see how recipes make any difference between a
build-time dependency such as a build tool, or a statically linked
library, so that some additional information should be input somewhere;
failing to provide that, since I don't feel like finding static library
symbols in binaries to perform a discovery, I just tell my clients to
distribute everything except their proprietary bits...
--
Jérôme
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 849 bytes --]
next prev parent reply other threads:[~2021-02-26 16:02 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 ` [licensing] " Mikko Rapeli
2021-02-26 16:01 ` Jérôme Carretero [this message]
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=20210226110158.6366efdb@pouet.cJ \
--to=cj-yocto@zougloub.eu \
--cc=licensing@lists.yoctoproject.org \
--cc=mikko.murto@hhpartners.fi \
--cc=mikko.rapeli@bmw.de \
--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.