Re: [PATCH 2/2] u-boot-script: Split packages by kernel

[Jan Kiszka <jan.kiszka@siemens.com>]

On 12.01.22 14:51, Schmidt, Adriaan (T CED SES-DE) wrote:
> Anton Mikanovich, Mittwoch, 12. Januar 2022 14:35:
>> 11.01.2022 18:56, Jan Kiszka wrote:
>>> On 11.01.22 16:05, Anton Mikanovich wrote:
>>>> 11.01.2022 15:03, Jan Kiszka wrote:
>>>>> It makes no sense to build the same package with the same content
>>>>> multiple times. We likely rather need to make it depend on a generic
>>>>> kernel package / create a generic kernel package name.
>>>>>
>>>>> Jan
>>>>
>>>> I'm afraid it will not help - moving this dependency into another
>>>> package will also move the issue into this new package.
>>>>
>>>
>>> It will. We just have to make u-boot-script depend on a generic kernel
>>> so that this package is only installed after some kernel - no matter
>>> which one - is already installed on the target image. There is NO
>>> dependency on the concrete kernel in this packages, just study it.
>>>
>>> Jan
>>
>> Can you please provide any details about how it can be implemented?
>> We have linux-image-generic package in Ubuntu, but not in Debian. And we
>> can't just create it, because of the same deps conflict issue in Isar.
>> I understood u-boot-script depends on any kernel, but we need to declare
>> this 'any' somehow.
> 
> OE has the concept of virtual providers:
> https://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#metadata-virtual-providers
> And it looks like the PREFERRED_PROVIDER_* variables are a bitbake feature, so it shouldn't be too hard to do something like this in Isar.
> 
> @Jan: I assume this is what you had in mind?

Yes and no: Yes, we would need just a provider, no, his won't help us as 
we need it as runtime dependency, and Debian kernel do not expose that. 
See my other reply.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux