Hi Joshua, all,
(happy Thanksgiving week-end, no emergency)
On 22.11.23 at 21:04, Michael Opdenacker via lists.openembedded.org wrote:
Available reference binary artifacts
------------------------------------
The first prototype will make the below binary artifacts publicly
available:
- Root filesystem images (as specified above)
- Binary package feeds (as specified above)
- PR (https://docs.yoctoproject.org/ref-manual/variables.html#term-PR)
database, so that people can manage updates to packages, by
importing the
database in a local PR server.
- Prebuilt object data ("Shared State cache) through a public server
(see
https://docs.yoctoproject.org/ref-manual/variables.html#term-SSTATE_MIRRORS),
to reuse binary output already built by the Yocto Project
autobuilders, to
reduce the compile time of additional packages.
- Hash Equivalence data through a public server
(see
https://docs.yoctoproject.org/bitbake/2.4/bitbake-user-manual/bitbake-user-manual-ref-variables.html#term-BB_HASHSERVE_UPSTREAM),
to increase the reusability of prebuilt objects.
I realize I completely overlooked the need to supply SPDX information.
While we can ship an SPDX description of the initial images, how can we
produce an update of this description after we install extra packages or
update existing ones through the binary package feeds?
Should the build system also generate "-spdx" packages for each component?
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1855):
https://lists.openembedded.org/g/openembedded-architecture/message/1855
Mute This Topic: https://lists.openembedded.org/mt/102755562/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
