All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uwe Geuder <jrswdnan22@snkmail.com>
To: yocto@yoctoproject.org
Subject: Re: Usage of yocto on different (production vs debug) scenarios
Date: Fri, 20 Apr 2018 15:26:32 +0300	[thread overview]
Message-ID: <87efja6p3b.fsf@snkmail.com> (raw)
In-Reply-To: <5ad9c6a8.08aa370a.e3f10.cf1eSMTPIN_ADDED_BROKEN@mx.google.com>

Following up on my own message...

On Fri, Apr 20, 2018 at 1:47 PM, Uwe Geuder <jrswdnan22snkmail.com> wrote:

> On Fri, Apr 20, 2018 at 10:59 AM, Iván Castell <icastell@nayarsystems.com> wrote:
>
[...]
>> However, things are getting complicated, because there is no way to
>> exclude some recipes easily. For example, we don't want iptables
>> installed on the debug image, but dependency chains include iptables
>> by default
>
> Doesn't blacklist do what you want?
>
> E.g. in your distro-production.conf
>
> PNBLACKLIST[iptables] = "we don't want iptables in product"
>

As recently mentioned in another thread on this list there is also
BBMASK.

https://lists.yoctoproject.org/pipermail/yocto/2018-April/040861.html

I don't know what would be the suitable/most idiomatic use cases for
PNBLACKLIST vs. BBMASK

Regards,

Uwe Geuder
Neuro Event Labs Oy
Tampere, Finland
uwe.gexder@neuroeventlabs.com (Bot check: fix one obvious typo)




  parent reply	other threads:[~2018-04-20 12:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-20  7:59 Usage of yocto on different (production vs debug) scenarios Iván Castell
2018-04-20 10:47 ` Uwe Geuder
     [not found] ` <5ad9c69c.1a72630a.6af4.6e06SMTPIN_ADDED_BROKEN@mx.google.com>
2018-04-20 12:02   ` Alan Martinovic
     [not found] ` <5ad9c6a8.08aa370a.e3f10.cf1eSMTPIN_ADDED_BROKEN@mx.google.com>
2018-04-20 12:26   ` Uwe Geuder [this message]
2018-04-20 13:21 ` Alex Kiernan
     [not found] ` <5ad9c6a5.d806630a.b3470.003fSMTPIN_ADDED_BROKEN@mx.google.com>
2018-04-23 15:10   ` Burton, Ross
2018-04-23 15:23     ` Iván Castell
2018-04-23 15:38       ` Burton, Ross
2018-04-24  6:31         ` Uwe Geuder
2018-04-24  6:45         ` Iván Castell
2018-04-25  8:49           ` Iván Castell

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=87efja6p3b.fsf@snkmail.com \
    --to=jrswdnan22@snkmail.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.