On Fri, 26 Feb 2021 15:21:10 +0000 "Mikko Rapeli" <mikko.rap...@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
pgpdbwN9KGnwc.pgp
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#52495): https://lists.yoctoproject.org/g/yocto/message/52495 Mute This Topic: https://lists.yoctoproject.org/mt/80929398/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
