From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Muhammad Shakeel <muhammad_shakeel@mentor.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] openssl: Add ca-certificates in RRECOMMENDS
Date: Wed, 25 Sep 2013 16:52:20 +0100 [thread overview]
Message-ID: <2149237.RBEObpR8u8@helios> (raw)
In-Reply-To: <5242FB37.6030104@mentor.com>
On Wednesday 25 September 2013 20:03:19 Muhammad Shakeel wrote:
> On 09/19/2013 06:03 PM, Shakeel, Muhammad wrote:
> > From: Muhammad Shakeel <muhammad_shakeel@mentor.com>
> >
> > In some situations ca-certificates are required along with openssl
> > to communicate securely, i.e. curl trying to fetch contents through https.
> >
> > Signed-off-by: Muhammad Shakeel <muhammad_shakeel@mentor.com>
> > ---
> >
> > meta/recipes-connectivity/openssl/openssl.inc | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/meta/recipes-connectivity/openssl/openssl.inc
> > b/meta/recipes-connectivity/openssl/openssl.inc index 78ff7ae..cf60d4b
> > 100644
> > --- a/meta/recipes-connectivity/openssl/openssl.inc
> > +++ b/meta/recipes-connectivity/openssl/openssl.inc
> > @@ -13,6 +13,8 @@ LIC_FILES_CHKSUM =
> > "file://LICENSE;md5=f9a8f968107345e0b75aa8c2ecaa7ec8">
> > DEPENDS = "perl-native-runtime"
> >
> > +RRECOMMENDS_${PN} = "ca-certificates"
> > +
> >
> > SRC_URI = "http://www.openssl.org/source/openssl-${PV}.tar.gz \
> >
> > "
> >
> > S = "${WORKDIR}/openssl-${PV}"
>
> Any feedback on this?
I could be wrong, but this doesn't seem like the right thing to do. Surely
individual *applications* that need ca-certificates in conjunction with OpenSSL
should be adding it to their RRECOMMENDS?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-09-25 15:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 13:03 [PATCH] openssl: Add ca-certificates in RRECOMMENDS Shakeel, Muhammad
2013-09-25 15:03 ` Muhammad Shakeel
2013-09-25 15:52 ` Paul Eggleton [this message]
2013-09-25 16:53 ` Khem Raj
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=2149237.RBEObpR8u8@helios \
--to=paul.eggleton@linux.intel.com \
--cc=muhammad_shakeel@mentor.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