All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: OpenEmbedded Core Mailing List
	<openembedded-core@lists.openembedded.org>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [PATCH v2] openssl: Use the c_rehash shell re-implementation for target
Date: Mon, 18 Mar 2019 23:18:18 +0000	[thread overview]
Message-ID: <1fb71bec0195779b572ef9870d2efbb2bea40abd.camel@linuxfoundation.org> (raw)
In-Reply-To: <81AEDE73-7DD8-4F69-BF8D-BC2BF92FFC06@gmail.com>

I was asked for my views on this thread.

OE is primarily targeting embedded systems and removing a perl
dependency from target is something we do care about and a significant
win. 

As such I'm tempted to merge this patch in for that reason. The fact
we're successfully using it at rootfs time is a good sign.

I was also made aware that on target ca-certificates is currently
broken by the last change in this area and this patch does in fact fix
that again. This tells us nobody uses it that heavily on target as
nobody noticed. It also means we could do with some better tests :/.

I think the commit message could use some work but IMO this patch
probably is worth it for OE.

I also note with interest that upstream are writing a C version as that
would solve much of this debate once and for all meaning we might not
have to carry this change forever. It would be good if the new upstream
version cared about sysroot style usage...

Cheers,

Richard




  reply	other threads:[~2019-03-18 23:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-18 13:36 [PATCH v2] openssl: Use the c_rehash shell re-implementation for target Otavio Salvador
2019-03-18 14:53 ` Alexander Kanavin
2019-03-18 16:00   ` Otavio Salvador
2019-03-18 16:09     ` Alexander Kanavin
2019-03-18 23:18       ` Richard Purdie [this message]
2019-03-18 23:26         ` Otavio Salvador
2019-03-18 23:34 ` Richard Purdie
2019-03-18 23:52   ` Andre McCurdy
2019-03-18 23:56     ` Richard Purdie
2019-03-19  0:10       ` Otavio Salvador

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=1fb71bec0195779b572ef9870d2efbb2bea40abd.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=otavio@ossystems.com.br \
    /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.