Steve,
Thanks for sending this out.
On 6/14/22 10:08, Steve Sakoman wrote:
At today's Yocto Project Technical Team Meeting Armin raised a
question about the proper way to set up local.conf to use the Yocto
Project state mirror for dunfell. This email is intended to bring
those not attending up to speed and trigger further discussion.
Armin pointed out that the sstate mirror setup section in
local.conf.sample seemed to be in error, and a subsequent web search
didn't yield any useful information on how to proceed. So at a minimum
we have a documentation issue!
Further discussion ensued, and from memory the following points were made:
1. A number of issues have been addressed in the master and kirkstone
branches which significantly improve the usability of the published
project sstate mirror. These improvements are not present in dunfell.
2. There are also improvements in progress for the infrastructure
exporting the sstate mirror.
3. On the autobuilder there are separate development sstate caches for
master, dunfell, and kirkstone. While not strictly necessary, this
was done to isolate potential sstate corruption to single branches.
4. The published sstate mirror is generated at release time, i.e. the
sstate cache from development builds is not used for the release
build.
There was also some discussion about next steps, and Richard suggested
this email to trigger a wider discussion. Potential steps:
1. Improve/fix the sstate cache section of local.conf.sample
This depends on #3 and #4 decision.
2. Improve documentation of sstate cache setup
I will open a two bugs for this: 1) SSTATE Mirror management , 2) Using
a SSTATE Mirror in the case of YP being the Mirror.
3. Consider a single sstate cache for all branches on the autobuilder
This would make it simpler to document and to have referenced in the
local.conf.sample as it would not change from release to release.
4. Consider a single sstate mirror for all branches
This option makes it easier to freeze on a release as the version
checkeout would match the SSTATE for that release. This may be more of
a Commercial use-case than this Projects.
I think from a Project stand point, having a unified SSTATE Mirror would
simplify a lot of things and improve our out-of-the-box experience for a
new user.
- armin
Hopefully others who attended the meeting can jump in if I missed or
misrepresented anything!
Steve
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#1560):
https://lists.openembedded.org/g/openembedded-architecture/message/1560
Mute This Topic: https://lists.openembedded.org/mt/91753971/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
