From: Saul Wold <sgw@linux.intel.com>
To: qiang.chen@windriver.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] openssl: create package for openssl configuration file
Date: Tue, 29 Oct 2013 08:36:49 -0700 [thread overview]
Message-ID: <526FD611.30304@linux.intel.com> (raw)
In-Reply-To: <1382937354-31622-1-git-send-email-qiang.chen@windriver.com>
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?
> FILES_libcrypto = "${base_libdir}/libcrypto${SOLIBS}"
> FILES_libssl = "${libdir}/libssl.so.*"
> FILES_${PN} =+ " ${libdir}/ssl/*"
> -FILES_${PN}-misc = "${libdir}/ssl/misc ${libdir}/ssl/openssl.cnf"
> +FILES_${PN}-misc = "${libdir}/ssl/misc"
> FILES_${PN}-dev += "${base_libdir}/libcrypto${SOLIBSDEV}"
>
> +# Add the openssl.cnf file to the openssl-conf package. Make the libcrypto
> +# package RRECOMMENDS on this package. This will enable the configuration
> +# file to be installed for both the base openssl package and the libcrypto
> +# package since the base openssl package depends on the libcrypto package.
> +FILES_openssl-conf = "${libdir}/ssl/openssl.cnf"
> +CONFFILES_openssl-conf = "${libdir}/ssl/openssl.cnf"
> +RRECOMMENDS_libcrypto += "openssl-conf"
> +
Same here, please use ${BPN} instead of openssl for the package
construction.
This actually points out an inssue with alot of other packages that use
${PN} for CONFFILES and packages that contain config files when setup on
a multilib system. I will be filing a general bug against this and
watching for patches.
Thanks
Sau!
> do_configure_prepend_darwin () {
> sed -i -e '/version-script=openssl\.ld/d' Configure
> }
>
next prev parent reply other threads:[~2013-10-29 15:36 UTC|newest]
Thread overview: 5+ 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 [this message]
2013-10-29 16:03 ` Paul Eggleton
2013-10-30 9:35 ` Qiang Chen
2013-10-30 9:33 ` Qiang Chen
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=526FD611.30304@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=qiang.chen@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox