All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Nicolas Dechesne <nicolas.dechesne@linaro.org>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Removing a package from an image
Date: Thu, 27 Jun 2013 07:27:56 -0600	[thread overview]
Message-ID: <51CC3DDC.9060209@mlbassoc.com> (raw)
In-Reply-To: <CAP71WjxSYZ0gs8bYw8uPsdHZpEbnU8nqCwBf=kpg0Er5efDycg@mail.gmail.com>

On 2013-06-27 06:57, Nicolas Dechesne wrote:
> On Thu, Jun 27, 2013 at 2:35 PM, Gary Thomas <gary@mlbassoc.com> wrote:
>> I'm using one of the machines from meta-fsl-arm (i.MX6) which
>> has this setting in the MACHINE.conf:
>>    MACHINE_EXTRA_RRECOMMENDS_append_mx6 = " imx-audio"
>>
>> While this is reasonable for most of these boards, I have one
>> which has no audio and I'd like to leave this package (and all
>> that it pulls with it) out of my images.
>>
>> I tried using this in my image recipe with no joy:
>>    MACHINE_EXTRA_RRECOMMENDS := "${@oe_filter_out('imx-audio',
>> '${MACHINE_EXTRA_RRECOMMENDS}', d)}"
>>
>> How can I "filter out" this extra/unwanted/setting?
>
> you can use BAD_RECOMMENDATIONS variable to list packages that must be
> filtered out during image creation. however BAD_RECOMMENDATIONS does
> not work with all IMAGE_FSTYPES. I think it only works with ipk for
> now.
>

I am using ipk and this does seem to work, thanks.

I'd still be interested to know if there is a more general mechanism
I can use for such things in the future.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  reply	other threads:[~2013-06-27 13:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 12:35 Removing a package from an image Gary Thomas
2013-06-27 12:57 ` Nicolas Dechesne
2013-06-27 13:27   ` Gary Thomas [this message]
2013-06-27 13:29     ` Nicolas Dechesne

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=51CC3DDC.9060209@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=nicolas.dechesne@linaro.org \
    --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.