All of lore.kernel.org
 help / color / mirror / Atom feed
From: kevin.strasser@linux.intel.com
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>, yocto@yoctoproject.org
Subject: Re: [meta-baryon][PATCH 1/3] packagegroup-core-tools: exclude packages that depend on x11
Date: Tue, 20 Nov 2012 13:05:24 -0800 (PST)	[thread overview]
Message-ID: <50669.10.7.202.84.1353445524.squirrel@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LY=TOBK_S_gNP9_BTS9Eua+XZDXS7eATVn7HKSCUJWqnQ@mail.gmail.com>

> On 20 November 2012 14:39, Paul Eggleton <paul.eggleton@linux.intel.com>
> wrote:
>>
>> This would work, but in this instance I think it would be better if we
>> fixed
>> the packagegroup-core-tools-* recipes in OE-Core so that the items that
>> require X11 are only included when x11 is in DISTRO_FEATURES, rather
>> than
>> making the change here.
>
> Isn't this what Jack Mitchell's commit (poky
> 627fd60c8c01bbc14ad375f6aa195469eab73d86) did, which make sysprof
> optional on X11?
>
> Ross
>

Ah, I was building against danny. That patch should fix
packagegroup-core-tools-profile, but packagegroup-core-tools-testapps
looks like it still always includes packages that depend on X11.

-Kevin


  reply	other threads:[~2012-11-20 21:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 20:18 [meta-baryon][PATCH 0/3] respect EXTRA_IMAGE_FEATURES Kevin Strasser
2012-11-19 20:20 ` [meta-baryon][PATCH 1/3] packagegroup-core-tools: exclude packages that depend on x11 Kevin Strasser
2012-11-20 14:39   ` Paul Eggleton
2012-11-20 14:56     ` Burton, Ross
2012-11-20 21:05       ` kevin.strasser [this message]
2012-11-19 20:20 ` [meta-baryon][PATCH 2/3] baryon-image: use parted instead of util-linux Kevin Strasser
2012-11-19 20:20 ` [meta-baryon][PATCH 3/3] baryon-image: change IMAGE_FEATURES assignment to "+=" Kevin Strasser

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=50669.10.7.202.84.1353445524.squirrel@linux.intel.com \
    --to=kevin.strasser@linux.intel.com \
    --cc=paul.eggleton@linux.intel.com \
    --cc=ross.burton@intel.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.