All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrej Valek <andrej.valek@siemens.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.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 08:33:21 +0200	[thread overview]
Message-ID: <e09f86d5-ef04-fa9c-8cbf-c0b0f4fa4172@siemens.com> (raw)
In-Reply-To: <59452b23-7470-588c-75fb-7445aaa13ba1@linux.intel.com>

Hi Alex,

On 06/07/18 15:13, Alexander Kanavin wrote:
> On 06/07/2018 10:32 AM, Andrej Valek wrote:
>> -do_install_append_class-native () {
>>           # Install a custom version of c_rehash that can handle sysroots properly.
>>           # This version is used for example when installing ca-certificates during
>>           # image creation.
>>           install -Dm 0755 ${WORKDIR}/openssl-c_rehash.sh ${D}${bindir}/c_rehash
>>           sed -i -e 's,/etc/openssl,${sysconfdir}/ssl,g' ${D}${bindir}/c_rehash
> 
> Why is this merged into the main do_install()? Please explain.
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.
> 
>> +        # Create SSL structure
>> +        install -d ${D}${sysconfdir}/ssl/
>> +        mv ${D}${libdir}/ssl-1.1/openssl.cnf \
>> +           ${D}${libdir}/ssl-1.1/certs \
>> +           ${D}${libdir}/ssl-1.1/private \
>> +           \
>> +           ${D}${sysconfdir}/ssl/
>> +        ln -sf ${sysconfdir}/ssl/certs ${D}${libdir}/ssl-1.1/certs
>> +        ln -sf ${sysconfdir}/ssl/private ${D}${libdir}/ssl-1.1/private
>> +        ln -sf ${sysconfdir}/ssl/openssl.cnf ${D}${libdir}/ssl-1.1/openssl.cnf
> 
> Please explain this change as well. Resend the patch with the 
> explanations included in the commit log or (better), the recipe itself.
During splitting to packages I have compared files with 1.0.2 and I
wanted to have same file structure. Anyway Debian is using this location
without modification and You don't like it, so I will revert it.

But note that bash-completion has the /etc path for openssl.cnf as
default search path... .
> 
> I would like to keep the new openssl recipe short and simple, and so 
> anything that adds lines and complication should be well justified. :)
> 
> Alex
> 

BR,
Andrej


  parent reply	other threads:[~2018-06-08  6:33 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 [this message]
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
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=e09f86d5-ef04-fa9c-8cbf-c0b0f4fa4172@siemens.com \
    --to=andrej.valek@siemens.com \
    --cc=alexander.kanavin@linux.intel.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 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.