Yocto is a community project. If you think such a tool is missing, patches are welcome. Talk to your employer about ability to contribute under your real name.
Alex On Wed 12. Feb 2020 at 0.50, Kent Dorfman <[email protected]> wrote: > 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 <[email protected]> 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 <[email protected]> > > 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? > >> > >> > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#48366): https://lists.yoctoproject.org/g/yocto/message/48366 Mute This Topic: https://lists.yoctoproject.org/mt/71172039/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
