Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] glib-networking: add PACKAGECONFIG for openssl
Date: Sat, 11 May 2019 09:58:49 +0300	[thread overview]
Message-ID: <20190511065849.GA24494@localhost> (raw)
In-Reply-To: <CAJ86T=V98Sv8re5sTq8w8KHAvHJKi2uSvDs4itO69SgXbi1JGQ@mail.gmail.com>

On Fri, May 10, 2019 at 04:00:45PM -0700, Andre McCurdy wrote:
>...
> It wasn't possible to build glib-networking with openssl until very
> recently but now that it's supported upstream I think we should
> switch.
> 
>   https://github.com/GNOME/glib-networking/blob/master/NEWS

This states clearly that we should not switch:

  This is the first stable release featuring the new OpenSSL backend.
  Please be advised that this new backend is still experimental and
  known to not work on some systems, including Debian. Linux
  distributions are encouraged to stick to the default build options,
  where OpenSSL is not yet enabled.


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  parent reply	other threads:[~2019-05-11  6:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-10 21:55 [PATCH] glib-networking: add PACKAGECONFIG for openssl Martin Jansa
2019-05-10 22:13 ` akuster808
2019-05-10 22:16   ` Khem Raj
2019-05-10 23:00     ` Andre McCurdy
2019-05-10 23:54       ` Khem Raj
2019-05-11  1:04         ` Martin Jansa
2019-05-11  1:17           ` Joshua Watt
2019-05-11  7:20             ` Adrian Bunk
2019-05-11 13:25               ` Joshua Watt
2019-05-11  6:58       ` Adrian Bunk [this message]
2019-05-14 12:02 ` Martin Jansa
2019-05-21 12:27   ` Martin Jansa

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=20190511065849.GA24494@localhost \
    --to=bunk@stusta.de \
    --cc=armccurdy@gmail.com \
    --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