All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] no-static-libs.inc: add gdb
Date: Tue, 1 Mar 2016 09:59:10 +0100	[thread overview]
Message-ID: <20160301085910.GB6407@jama> (raw)
In-Reply-To: <CAJTo0LbSUxP=yUD2Ga8=TeT-eudZaFjrMP7HKq-yv0B9RfK6sw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 654 bytes --]

On Tue, Mar 01, 2016 at 08:40:13AM +0000, Burton, Ross wrote:
> On 1 March 2016 at 00:43, Martin Jansa <martin.jansa@gmail.com> wrote:
> 
> > OE qemux86@ ~/build/oe-core $ cat
> > meta-qt5/recipes-devtools/gdb/gdb_%.bbappend
> > PACKAGECONFIG ??= "python"
> >
> 
> Having fixed number of these myself it's definitely best practise to use
> PACKAGECONFIG_append and _remove in a bbappend.

That's what I did, but on other hand it's harder for DISTRO to remove
python if meta-qt5 bbappend uses _append.

So I'm thinking about changing it to
PACKAGECONFIG ??= "readline python"

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

  reply	other threads:[~2016-03-01  8:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-29 19:10 [PATCH] no-static-libs.inc: add gdb Martin Jansa
2016-02-29 20:40 ` Richard Purdie
2016-02-29 20:43   ` Burton, Ross
2016-02-29 20:50     ` Andre McCurdy
2016-02-29 21:30       ` Martin Jansa
2016-03-01  0:43         ` Martin Jansa
2016-03-01  8:04           ` Richard Purdie
2016-03-01  8:11             ` Martin Jansa
2016-03-01  8:40           ` Burton, Ross
2016-03-01  8:59             ` Martin Jansa [this message]
2016-03-03 15:01       ` Martin Jansa
2016-03-03 17:19       ` Burton, Ross
2016-03-03 20:51         ` Burton, Ross

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=20160301085910.GB6407@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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.