From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: 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 15:45:23 +0300 [thread overview]
Message-ID: <58fa6d36-737b-da77-d1ec-f72d50c75e5d@linux.intel.com> (raw)
In-Reply-To: <78456fb6-d8a1-c681-792a-36e78d7fb790@siemens.com>
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
next prev parent reply other threads:[~2018-06-11 12:44 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 [this message]
2018-06-11 17:54 ` Peter Kjellerstedt
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=58fa6d36-737b-da77-d1ec-f72d50c75e5d@linux.intel.com \
--to=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