Re: [Openembedded-architecture] Recipes which should always be upgraded on stable branches

["Yoann Congal" <yoann.congal@smile.fr>]

On Thu Feb 26, 2026 at 12:50 AM CET, Mark Hatle via lists.openembedded.org wrote:
> On 2/25/26 11:44 AM, Paul Barker wrote:
>> Hi all,
>> 
>> I've been briefly discussing stable branch update policy with Yoann.
>> There's a few recipes in openembedded-core which I would like to propose
>> that we always update to the latest version on LTS and stable branches.
>> These are recipes typically providing data that is expected to change
>> over time, with little or no code.
>> 
>> You could say ca-certificates is already covered by the fact that
>> security fixes are acceptable for example, but a clearer policy would be
>> better.
>> 
>> Any policy change will go to the TSC for approval, the goal here is to
>> get some review and input so that a concrete proposal can be put
>> forward.
>> 
>> The recipes that come to my mind are:
>> 
>> - ca-certificates: To allow access to HTTPS resources we need to keep
>>    these up-to-date.
>> 
>>      - Keeping this up-to-date is common practice in other distros.

Agreed but since CAs can be removed from the list, there is a
probability for breakage. We should acknowledge that. By spelling out
the CA addition/removal in the release notes maybe?

>> - tzdata: To stay up to date with timezone or daylight savings changes.
>> 
>>      - Debian takes upgrades to this on stable branches
>>        (see https://tracker.debian.org/pkg/tzdata).
>
> I agree completely for the above two items.  Keeping these current is really 
> important and history has shown that updating them doesn't cause issues.
>
>
> The one below I don't have any experience with, so no opinion.
>
>> - mobile-broadband-provider-info: To stay up to date with provider
>>    changes.
>> 
>>      - The README file for this project says "The Package contains only
>>        informational files so it's safe for distributions to grab updates
>>        even during feature freeze and maintenance stages."
>> 
>> What opinions do other folks have?

I also agree with updating those. I've looked at
mobile-broadband-provider-info for a recent stable upgrade and merged
it.

>> Are there any other recipes we should include in this list?

In addition of the wireless-regdb suggestion from Ankur, maybe we should
consider hwdata:
> hwdata contains various hardware identification and configuration data,
> such as the pci.ids and usb.ids databases.
I have no direct experience with it but it does seem to match this list.

>> Best regards,

Regards,
-- 
Yoann Congal
Smile ECS