From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] openssl: create package for openssl configuration file
Date: Tue, 29 Oct 2013 16:03:36 +0000 [thread overview]
Message-ID: <2319343.tLITFFHSjA@helios> (raw)
In-Reply-To: <526FD611.30304@linux.intel.com>
On Tuesday 29 October 2013 08:36:49 Saul Wold wrote:
> On 10/27/2013 10:15 PM, qiang.chen@windriver.com wrote:
> > From: Qiang Chen <qiang.chen@windriver.com>
> >
> > * Add the openssl-conf package to the list of packages to
> >
> > be created. This package contains the openssl.cnf file
> > which is used by both the openssl executable in the
> > openssl package and the libcrypto library.
> >
> > * This is to avoid messages like:
> > WARNING: can't open config file: /usr/lib/ssl/openssl.cnf
> >
> > * When running "openssl req" to request and generate a certificate
> >
> > the command will fail without the openssl.cnf file being
> > installed on the target system.
> >
> > * Made this package an RRECOMMENDS for libcrypto since:
> > * libcrypto is a RDEPENDS for the openssl package
> > * Users can specify a configuration file at another
> >
> > location so it is not stricly required and many
> > commands will work without it (with warnings)
> >
> > Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
> > Signed-off-by: Qiang Chen <qiang.chen@windriver.com>
> > ---
> >
> > meta/recipes-connectivity/openssl/openssl.inc | 12 ++++++++++--
> > 1 file changed, 10 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta/recipes-connectivity/openssl/openssl.inc
> > b/meta/recipes-connectivity/openssl/openssl.inc index 78ff7ae..f4b786a
> > 100644
> > --- a/meta/recipes-connectivity/openssl/openssl.inc
> > +++ b/meta/recipes-connectivity/openssl/openssl.inc
> > @@ -33,13 +33,21 @@ export AS = "${CC} -c"
> >
> > inherit pkgconfig siteinfo multilib_header
> >
> > -PACKAGES =+ "libcrypto libssl ${PN}-misc"
> > +PACKAGES =+ "libcrypto libssl ${PN}-misc openssl-conf"
>
> How about ${BPN}-conf here instead?
Does this work when two multilib variants produce the same package name? I
suspect you'll get warnings.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-10-29 16:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 5:15 [PATCH] openssl: create package for openssl configuration file qiang.chen
2013-10-29 15:36 ` Saul Wold
2013-10-29 16:03 ` Paul Eggleton [this message]
2013-10-30 9:35 ` Qiang Chen
2013-10-30 9:33 ` Qiang Chen
-- strict thread matches above, loose matches on Subject: below --
2010-12-16 17:31 Chase Maupin
2010-12-18 7:21 ` Roman I Khimov
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=2319343.tLITFFHSjA@helios \
--to=paul.eggleton@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.