From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
Andrej Valek <andrej.valek@siemens.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3 1/2] openssl-1.1: rework packaging
Date: Mon, 11 Jun 2018 17:54:28 +0000 [thread overview]
Message-ID: <99402ec2af244deca7b1dd9b6b9f799d@XBOX02.axis.com> (raw)
In-Reply-To: <58fa6d36-737b-da77-d1ec-f72d50c75e5d@linux.intel.com>
> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Alexander Kanavin
> Sent: den 11 juni 2018 14:45
> To: Andrej Valek <andrej.valek@siemens.com>
> Cc: OE-core <openembedded-core@lists.openembedded.org>
> Subject: Re: [OE-core] [PATCH v3 1/2] openssl-1.1: rework packaging
>
> On 06/11/2018 09:19 AM, Andrej Valek wrote:
> > Hi Alex,
> >
> > I have tested your branch and seems to be, that openssl is working
> > correctly.
> >
> > We are now using original (perl) c_rehash script, but dependency to perl
> > is missing. Are you ok with adding runtime dependency to bin package?
> > Just for notice, it will install perl on target.
>
> Yes, of course. If c_rehash needs perl interpreter to run, then it has
> to pull it in.
>
> Alex
Any reason the openssl-c_rehash.sh reimplementation of c_rehash
as a shell script is not used for target with openssl-1.1? It is
currently used for both native and target for openssl-1.0, and
native for openssl-1.1. Using it would avoid the dependency on
perl for target, which at least for us is not an option to have
(and we do need c_rehash for target).
//Peter
next prev parent reply other threads:[~2018-06-11 17:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-07 7:25 [PATCH] feat(openssl-1.1): rework packaging Andrej Valek
2018-06-07 7:32 ` [PATCH v2] " Andrej Valek
2018-06-07 13:13 ` Alexander Kanavin
2018-06-07 13:26 ` Alexander Kanavin
2018-06-08 6:33 ` Andrej Valek
2018-06-08 7:48 ` Andrej Valek
2018-06-08 9:48 ` Alexander Kanavin
2018-06-08 11:31 ` Andrej Valek
2018-06-08 11:47 ` Alexander Kanavin
2018-06-08 14:04 ` [PATCH v3 1/2] openssl-1.1: " Andrej Valek
2018-06-08 15:57 ` Alexander Kanavin
2018-06-11 6:19 ` Andrej Valek
2018-06-11 12:45 ` Alexander Kanavin
2018-06-11 17:54 ` Peter Kjellerstedt [this message]
2018-06-11 18:15 ` Alexander Kanavin
2018-06-11 13:30 ` [PATCH v4 1/3] openssl-1.1: fix c_rehash perl errors Andrej Valek
2018-06-11 13:30 ` [PATCH v4 2/3] openssl-1.1: rework packaging Andrej Valek
2018-06-11 13:30 ` [PATCH v4 3/3] openssl-1.1: /etc/ssl location compatibility Andrej Valek
2018-07-09 12:06 ` Andrej Valek
2018-07-09 12:44 ` Alexander Kanavin
2018-06-08 14:04 ` [PATCH v3 2/2] " Andrej Valek
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=99402ec2af244deca7b1dd9b6b9f799d@XBOX02.axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=alexander.kanavin@linux.intel.com \
--cc=andrej.valek@siemens.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