Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andreas Oberritter <obi@opendreambox.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/5] libsoup-2.4: don't depend on libgnome-keyring unless x11 is defined
Date: Fri, 24 Feb 2012 14:27:21 +0100	[thread overview]
Message-ID: <4F479039.7090708@opendreambox.org> (raw)
In-Reply-To: <20120224081006.GA2519@sakrah.homelinux.org>

On 24.02.2012 09:10, Khem Raj wrote:
> On (22/02/12 13:56), Koen Kooi wrote:
>>
>> Op 22 feb. 2012, om 12:26 heeft Andreas Oberritter het volgende geschreven:
>>
>>> * Drop dependency on GNOME if x11 is disabled.
>>>
>>> Signed-off-by: Andreas Oberritter <obi@opendreambox.org>
>>> ---
>>> meta/recipes-support/libsoup/libsoup-2.4_2.36.1.bb |    4 ++--
>>> 1 files changed, 2 insertions(+), 2 deletions(-)
>>>
>>> diff --git a/meta/recipes-support/libsoup/libsoup-2.4_2.36.1.bb b/meta/recipes-support/libsoup/libsoup-2.4_2.36.1.bb
>>> index 8e6ef26..861a1aa 100644
>>> --- a/meta/recipes-support/libsoup/libsoup-2.4_2.36.1.bb
>>> +++ b/meta/recipes-support/libsoup/libsoup-2.4_2.36.1.bb
>>> @@ -6,9 +6,9 @@ LICENSE = "LGPLv2"
>>> LIC_FILES_CHKSUM = "file://COPYING;md5=5f30f0716dfdd0d91eb439ebec522ec2"
>>>
>>> SECTION = "x11/gnome/libs"
>>> -PR = "r1"
>>> +PR = "r2"
>>>
>>> -DEPENDS = "glib-2.0 gnutls libxml2 libproxy sqlite3 libgnome-keyring"
>>> +DEPENDS = "glib-2.0 gnutls libxml2 libproxy sqlite3 ${@base_contains('DISTRO_FEATURES', 'x11', 'libgnome-keyring', '', d)}"
>>
>> that one likely needs a --disable-something to be deterministic.
> 
> may be --without-gnome or --disable-gnome-keyring ?

The flag --without-gnome is right. I've updated this patch [1],
but I'm waiting before resubmitting it, because after Richard's
comments I'm unsure which distro feature should be tested or
whether PACKAGECONFIG should be used.

Regards,
Andreas

[1] http://git.openembedded.org/openembedded-core-contrib/commit/?h=obi/current&id=5c7c62268aa56a5d4d58764653ef95a9deb683ad



  reply	other threads:[~2012-02-24 13:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-22 11:26 [RFC][PATCH 0/5] drop dependency on GNOME if x11 is disabled Andreas Oberritter
2012-02-22 11:26 ` [PATCH 1/5] libsoup-2.4: don't depend on libgnome-keyring unless x11 is defined Andreas Oberritter
2012-02-22 12:56   ` Koen Kooi
2012-02-24  8:10     ` Khem Raj
2012-02-24 13:27       ` Andreas Oberritter [this message]
2012-02-24 15:05         ` Richard Purdie
2012-02-22 11:26 ` [PATCH 2/5] libproxy: don't depend on gconf " Andreas Oberritter
2012-02-22 12:57   ` Koen Kooi
2012-02-22 11:26 ` [PATCH 3/5] gconf.bbclass: don't add dependencies or hooks " Andreas Oberritter
2012-02-22 11:26 ` [PATCH 4/5] gtk-icon-cache.bbclass: " Andreas Oberritter
2012-02-22 11:26 ` [PATCH 5/5] gnomebase.bbclass: skip packages inheriting gnomebase " Andreas Oberritter
2012-02-22 13:31 ` [RFC][PATCH 0/5] drop dependency on GNOME if x11 is disabled Richard Purdie
2012-02-22 14:54   ` Andreas Oberritter
2012-02-22 15:00     ` Paul Eggleton
2012-02-22 21:24     ` Richard Purdie
2012-02-23  1:35       ` Andreas Oberritter

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=4F479039.7090708@opendreambox.org \
    --to=obi@opendreambox.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox