All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: openembedded-core@lists.openembedded.org
Cc: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>
Subject: [PATCH 0/3] Improve x11 distro_feature checks
Date: Mon, 29 Oct 2012 09:28:47 +0000	[thread overview]
Message-ID: <1351502930-2348-1-git-send-email-ml@communistcode.co.uk> (raw)

From: Jack Mitchell <jack.mitchell@dbbroadcast.co.uk>

Improvement to the detection of the x11 distro_feature in a few recipes
with the final achievement being that GTK+ is no longer required in 
core-image-minimal if dbg-pkgs, tools-profile and tools-debug are enabled 
when x11 is not in distro_features.

V2

Added PR bumps to all recipes

Jack Mitchell (3):
  latencytop: disable GTK and remove gtk+ dependacy
  packagegroup-core-tools-profile: include sysprof only if x11 is
    distro feature
  babeltrace: fix depends

 .../packagegroups/packagegroup-core-tools-profile.bb        |  4 +++-
 .../latencytop/latencytop-0.5/latencytop-makefile.patch     | 13 +++++++------
 meta/recipes-kernel/latencytop/latencytop_0.5.bb            |  6 ++++--
 meta/recipes-kernel/lttng-2.0/babeltrace_0.12.bb            |  2 +-
 4 files changed, 15 insertions(+), 10 deletions(-)

-- 
1.8.0




             reply	other threads:[~2012-10-29  9:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-29  9:28 Jack Mitchell [this message]
2012-10-29  9:28 ` [PATCH 1/3] latencytop: disable GTK and remove gtk+ dependacy Jack Mitchell
2012-10-29  9:28 ` [PATCH 2/3] packagegroup-core-tools-profile: include sysprof only if x11 is distro feature Jack Mitchell
2012-10-29  9:28 ` [PATCH 3/3] babeltrace: fix depends Jack Mitchell
  -- strict thread matches above, loose matches on Subject: below --
2012-10-29  9:28 [PATCH 0/3] Improve x11 distro_feature checks Jack Mitchell
2012-10-29  9:30 ` Jack Mitchell
2012-10-26 13:37 Jack Mitchell
2012-10-28  1:12 ` Saul Wold

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=1351502930-2348-1-git-send-email-ml@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=jack.mitchell@dbbroadcast.co.uk \
    --cc=openembedded-core@lists.openembedded.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.