was able to modify the vendor's machine/inc file to remove the
offending package.
Since the whole tree is in git now, I suppose that's OK, but I do wish
yocto had better tools for managing inclusions and introspection into
what is in an image and at what level it's defined.


On 2/11/20, Alexander Kanavin <alex.kanavin@...> wrote:
> You need to modify the image recipe so that those packagegroups are not
> pulled in. If you cannot do that because it's in a layer controlled by
> someone else etc, then make a new image recipe, and build that image
> instead.
>
> Alex
>
> On Tue, 11 Feb 2020 at 18:05, Kent Dorfman <kent.dorfman766@...>
> wrote:
>
>> My vendor finally realized that I needed a full yocto release and not
>> the eSDK.  Anyway, I can build their image, but when I modify the
>> kernel to remove CAN drivers I get the errors that
>>
>> packagegroup-can-support
>> packagegroup-ow-support
>>
>> are required.
>>
>> What is the "yocto way"  to remove those packages and dependencies
>> from the build?
>>
>>
>