Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Li, Xin" <lixin.fnst@cn.fujitsu.com>
Cc: Anders Darander <anders@chargestorm.se>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] curl: Modify PACKAGECONFIG to enable openssl
Date: Thu, 16 Jul 2015 13:43:44 +0200	[thread overview]
Message-ID: <20150716114344.GA2134@jama> (raw)
In-Reply-To: <A8FC939F80655644A89BB21CCD3741E87390E153@G08CNEXMBPEKD02.g08.fujitsu.local>

[-- Attachment #1: Type: text/plain, Size: 3115 bytes --]

On Thu, Jul 16, 2015 at 03:54:04AM +0000, Li, Xin wrote:
> Hi, Anders
> 
> Thanks for your replay.
> 
> > Subject: Re: [OE-core] [PATCH] curl: Modify PACKAGECONFIG to enable openssl
> > 
> > * Li xin <lixin.fnst@cn.fujitsu.com> [150612 05:41]:
> > 
> > > Enabled openssl defalutly to use https, just like Ubuntu and Red Hat do.
> > 
> > > Signed-off-by: Li Xin <lixin.fnst@cn.fujitsu.com>
> > > ---
> > 
> > > -PACKAGECONFIG ??= "${@bb.utils.contains("DISTRO_FEATURES", "ipv6", "ipv6",
> > "", d)} gnutls zlib"
> > > +PACKAGECONFIG ??= "${@bb.utils.contains("DISTRO_FEATURES", "ipv6", "ipv6",
> > "", d)} ssl zlib"
> > 
> > I think you need to motivate why you're changing from gnutls to ssl
> > (openssl) here.
> > 
> > Not that I'm personally against it. I've occasionally done the same thing locally. But
> > this is a change of the defaults, and the default dependencies. Thus, it needs to
> > have a good motivation.
> 
> The motivation is as following:
> Curl depends on gnutls and gnutls depends on gmp, but the LICENSE of gmp is LGPLv3.
> If the users do not want to use the LGPLv3 recipes(the rpm of gmp is not be installed), there will be an error when using https.
> Such as:
> ----------------
> # curl -k https://192.168.246.1
> curl: error while loading shared libraries: libgmp.so.10: cannot open shared object file: No such file or directory 
> ----------------
> But after changing gnutls to ssl in PACKAGECONFIG, there will be no errors.

What about returning gmp v4.2.1 which was last LGPLv2 version?

This says, it's OK to remove v4.2.1, because v6.0.0 is dual licensed:
http://git.openembedded.org/openembedded-core/commit/?id=f181c6ce8b364fbf761a456d998ab78fbd751f35

but it's dual licensed under GPLv2+ | LGPLv3+ and using GPLv2 libraries
isn't acceptable by some projects.

So I would vote for returning v4.2.1.

> > 
> > >  PACKAGECONFIG_class-native = "ipv6 ssl zlib"
> > >  PACKAGECONFIG_class-nativesdk = "ipv6 ssl zlib"
> > 
> > > @@ -36,6 +36,7 @@ EXTRA_OECONF = "--without-libidn \
> > >                  --disable-ldap \
> > >                  --disable-ldaps \
> > >
> > > --with-ca-bundle=${sysconfdir}/ssl/certs/ca-certificates.crt \
> > > +                --with-libssh2 \
> > 
> > NACK.
> > 
> > We have a PACKAGECONFIG för libssh2, which defaults to off. Do /not/ enable it
> > directly in EXTRA_OECONF. This will break builds (at least the determinism of
> > builds).
> > 
> Yes.
> Enabling -with-libssh2 in EXTRA_OECONF is not right.
> My goal is to let sftp supported by curl, by adding libssh2 in PACKAGECONFIG.
> But libssh2 is not in OE-core by default. 
> And I think there may be someone else want to use libssh2.
> So how about moving libssh2 recipe from Meta-oe to OE-core? :)
> 
> Thank you very much.
> 
> Regards,
> Li
> 
> -- 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]

      reply	other threads:[~2015-07-16 11:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12  3:40 [PATCH] curl: Modify PACKAGECONFIG to enable openssl Li xin
2015-06-12  8:29 ` Anders Darander
2015-06-12  9:23   ` Li, Xin
2015-07-16  3:54   ` Li, Xin
2015-07-16 11:43     ` Martin Jansa [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=20150716114344.GA2134@jama \
    --to=martin.jansa@gmail.com \
    --cc=anders@chargestorm.se \
    --cc=lixin.fnst@cn.fujitsu.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