Hi Paul,
>> kernel-module-nls-utf8 (which goes into the image)
>> kernel-module-input (which does not make it to the image)
>>
>> and both appear in RRECOMENDS_packagegroup-base.
>
> You definitely have the kernel-module-input package created - right? Because
> it's an RRECOMMENDS, that package
On Friday 16 October 2015 09:38:56 Carlos Sánchez de La Lama wrote:
> Hi Paul,
>
> >> I have some doubts on how package inclusion in images is determined. For
> >> example, when building core-image-base, I would say that both
> >>
> >> kernel-module-uvesafb
> >> kernel-module-input
> >>
> >> are
Hi Paul,
>> I have some doubts on how package inclusion in images is determined. For
>> example, when building core-image-base, I would say that both
>>
>> kernel-module-uvesafb
>> kernel-module-input
>>
>> are recommended (through RRECOMENDS in packagegroup-base).
>
> I don't see a reference to
On Thursday 15 October 2015 18:03:13 Carlos Sánchez de La Lama wrote:
> Hi all,
>
> I have some doubts on how package inclusion in images is determined. For
> example, when building core-image-base, I would say that both
>
> kernel-module-uvesafb
> kernel-module-input
>
> are recommended (throug
