All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: "Smith, Virgil" <Virgil.Smith@flir.com>,
	"Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: yocto@yoctoproject.org
Subject: Re: recipe removing (some)contents of /etc
Date: Thu, 14 May 2015 17:41:55 +0100	[thread overview]
Message-ID: <1622249.AcBk4fCPKl@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <F14AEF751653024287138321000C846AF4821E78@BOS-DAG1.zone1.flir.net>

On Thursday 14 May 2015 16:34:56 Smith, Virgil wrote:
> > > Change
> > > IMAGE_INSTALL += “canlogger”
> > > to
> > > IMAGE_INSTALL_append = “ canlogger”
> > > or possibly better
> > > EXTRA_IMAGE_INSTALL_append = “ canlogger”
> >
> >
> >
> >   if you're putting this in local.conf, i'm pretty sure the preferred
> >   syntax is just:
> EXTRA_IMAGE_INSTALL = "canlogger"
> 
> 
> Yes, I think rday is correct and the intended purpose of EXTRA_IMAGE_INSTALL
> is to be used entirely from local.conf and thereby avoid the += vs ?= vs
> _append issues I mentioned.  At least EXTRA_IMAGE_FEATURES is listed this
> way in the Yocto manual.

There's no such thing as EXTRA_IMAGE_INSTALL, not in the core system anyway. 
There is CORE_IMAGE_EXTRA_INSTALL though which you can add to with += (since 
there aren't any default items in it, unlike IMAGE_INSTALL).

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2015-05-14 16:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 15:27 recipe removing (some)contents of /etc Oliver
2015-05-14 15:36 ` Gary Thomas
2015-05-14 16:14 ` Smith, Virgil
2015-05-14 16:18   ` Robert P. J. Day
2015-05-14 16:34     ` Smith, Virgil
2015-05-14 16:41       ` Paul Eggleton [this message]
2015-05-14 16:48         ` Robert P. J. Day
2015-05-14 21:36         ` Oliver
2015-05-14 22:01           ` Gary Thomas
2015-05-15 11:07             ` Oliver

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=1622249.AcBk4fCPKl@peggleto-mobl.ger.corp.intel.com \
    --to=paul.eggleton@linux.intel.com \
    --cc=Virgil.Smith@flir.com \
    --cc=rpjday@crashcourse.ca \
    --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.