Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [meta-oe][PATCH] pidgin: explicitly disable nss
Date: Thu, 17 May 2012 12:28:33 +0100	[thread overview]
Message-ID: <1682908.OEHQSIBnpA@helios> (raw)
In-Reply-To: <20120517112446.GG3164@jama.jama.net>

On Thursday 17 May 2012 13:24:46 Martin Jansa wrote:
> On Thu, May 17, 2012 at 12:20:12PM +0100, Paul Eggleton wrote:
> > On Thursday 17 May 2012 08:58:39 Martin Jansa wrote:
> > > * sometimes it leaks from meta-chromium and breaks pidgin build
> > 
> > Does that mean SSL will be unavailable in pidgin after this change?
> 
> No it means that it should always detect gnutls, not nss when chromium
> was built before pidgin.

OK, cool, just checking.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2012-05-17 11:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17  6:58 [meta-oe][PATCH] pidgin: explicitly disable nss Martin Jansa
2012-05-17 11:20 ` Paul Eggleton
2012-05-17 11:24   ` Martin Jansa
2012-05-17 11:28     ` Paul Eggleton [this message]

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=1682908.OEHQSIBnpA@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@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