From: "Denys Dmytriyenko" <denis@denix.org>
To: Kent Dorfman <kent.dorfman766@gmail.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: [yocto] how to remove a package from image
Date: Tue, 11 Feb 2020 21:33:17 -0500 [thread overview]
Message-ID: <20200212023317.GV4735@denix.org> (raw)
In-Reply-To: <CAK4PFCXVMVOtHAEuxK5yexUFTKTZ+1naFJR-HYCyvAC-085KrQ@mail.gmail.com>
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@gmail.com> 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@gmail.com>
> > 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?
> >>
> >>
> >
>
next prev parent reply other threads:[~2020-02-12 2:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 17:05 how to remove a package from image Kent Dorfman
2020-02-11 17:33 ` [yocto] " Alexander Kanavin
2020-02-11 23:50 ` Kent Dorfman
2020-02-12 2:33 ` Denys Dmytriyenko [this message]
2020-02-12 7:15 ` Alexander Kanavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200212023317.GV4735@denix.org \
--to=denis@denix.org \
--cc=kent.dorfman766@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.