yocto@lists.yoctoproject.org | how to remove a package from image

Home Messages Hashtags Subgroups

Date Date 1 - 5 of 5

how to remove a package from image

Kent Dorfman <kent.dorfman766@...> #48359 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?
More All Messages By This Member
Alexander Kanavin #48360 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 toggle quoted message Show quoted text 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?
More All Messages By This Member
Kent Dorfman <kent.dorfman766@...> #48363 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. toggle quoted message Show quoted text 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?
More All Messages By This Member
Denys Dmytriyenko #48364 On Tue, Feb 11, 2020 at 06:50:09PM -0500, Kent Dorfman 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. Images are supposed to be all custom. It means if you cannot easily use one of the existing images, you create your own. There are ways to bbappend an existing image and mangle its content, but it's usually not worth the trouble when you can simply create your own. -- Denys 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?
More All Messages By This Member
Alexander Kanavin #48366 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 toggle quoted message Show quoted text On Wed 12. Feb 2020 at 0.50, Kent Dorfman <kent.dorfman766@...> 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 <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? >> >> >
More All Messages By This Member

1 - 5 of 5

1

Previous Topic Next Topic

Home Hashtags Subgroups Terms