Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] libproxy: add dependency on glib-2.0
Date: Fri, 17 Aug 2012 22:41:57 +0100	[thread overview]
Message-ID: <1345239717.27428.22.camel@ted> (raw)
In-Reply-To: <502E886E.30002@windriver.com>

On Fri, 2012-08-17 at 14:07 -0400, Paul Gortmaker wrote:
> On 12-08-17 12:57 PM, Richard Purdie wrote:
> > On Mon, 2012-08-13 at 18:43 -0400, Paul Gortmaker wrote:
> >> Without this, you will get occasional build failures if libproxy
> >> tries to build before the glib headers are placed in the sysroot.
> >>
> >> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
> >>
> >> diff --git a/meta/recipes-support/libproxy/libproxy_0.4.7.bb b/meta/recipes-support/libproxy/libproxy_0.4.7.bb
> >> index 7e3cf27..a39e3a8 100644
> >> --- a/meta/recipes-support/libproxy/libproxy_0.4.7.bb
> >> +++ b/meta/recipes-support/libproxy/libproxy_0.4.7.bb
> >> @@ -6,7 +6,7 @@ LICENSE = "LGPLv2.1+"
> >>  LIC_FILES_CHKSUM = "file://COPYING;md5=7d7044444a7b1b116e8783edcdb44ff4 \
> >>                      file://utils/proxy.c;beginline=1;endline=18;md5=55152a1006d7dafbef32baf9c30a99c0"
> >>  
> >> -DEPENDS = "gconf"
> >> +DEPENDS = "gconf glib-2.0"
> >>  
> > 
> > We've gone around in circles on this and had issues over circular
> > dependencies. The bottom line is that we don't need glib-2.0 here, we
> > want to disable the glib-2.0 using components of libproxy. I don't know
> 
> Fair enough.
> 
> Can we _finally_ fix the mailing lists to not override the To/Cc lines
> with crap Reply-To: lines?  Once again I almost missed seeing this reply,
> since I was no longer on the To/Cc.
> 
> AFAICT, all were in agreement that it was broken, but it never got fixed.

There were a few things causing problems here such as lost admin access.
Those have been resolved and I just changed the setting that I think was
causing the problems. Let me know if there are still issues...

Cheers,

Richard




  parent reply	other threads:[~2012-08-17 21:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-13 22:43 [PATCH] libproxy: add dependency on glib-2.0 Paul Gortmaker
2012-08-17 16:57 ` Richard Purdie
2012-08-17 18:07   ` Paul Gortmaker
2012-08-17 18:19     ` McClintock Matthew-B29882
2012-08-17 21:41     ` Richard Purdie [this message]
2012-08-20 13:50       ` Paul Gortmaker
2012-08-20 16:15         ` McClintock Matthew-B29882
  -- strict thread matches above, loose matches on Subject: below --
2013-04-03 12:23 [PATCH] libproxy: add dependency on libffi Alex DAMIAN
2013-04-03 15:20 ` [PATCH] libproxy: add dependency on glib-2.0 Alex DAMIAN
2013-04-03 15:33   ` 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=1345239717.27428.22.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.gortmaker@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox