Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Andrej Valek <andrej.valek@siemens.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] feat(openssl-1.1): rework packaging
Date: Fri, 8 Jun 2018 12:48:52 +0300	[thread overview]
Message-ID: <0edc5efa-5836-2b76-7af1-a4261a345e56@linux.intel.com> (raw)
In-Reply-To: <c407b9de-5921-0512-eeba-9ea6f9464386@siemens.com>

On 06/08/2018 10:48 AM, Andrej Valek wrote:
> after more testing, I think creating ${sysconfdir}/ssl links is highly
> recommended. ca-certificate updating script (+ many other tools) has
> hard-coded path to /etc/ssl. Debian has multiple links in /usr/lib/ssl/
> to /etc/ssl/.

Right. Can you explain this in a comment in the recipe itself, and make 
the change as a separate commit please?

> c_rehash was not working on target exactly as on native. (Same perl
> erros). So I have copied this stuff from 1.0.2, it is working on both
> platforms as well.

Can you however try to look deeper into why it fails on target? For the 
target, I would much rather use the upstream's version than our custom 
script, so we don't have to deal with bit-rot and extra maintenance. The 
custom script then would only have a limited, controlled purpose of 
running under bitbake.

Alex


  reply	other threads:[~2018-06-08  9:48 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 [this message]
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
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=0edc5efa-5836-2b76-7af1-a4261a345e56@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