From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] openssl: remove binary install option
Date: Sat, 9 Jan 2016 10:13:58 -0300 [thread overview]
Message-ID: <56910796.5040204@zacarias.com.ar> (raw)
In-Reply-To: <5690475B.2090201@mind.be>
On 08/01/16 20:33, Arnout Vandecappelle wrote:
> On 05-01-16 13:35, Gustavo Zacarias wrote:
>> In preparation for the libssl virtual and libressl inclusion, also
>> keeping with the KISS principle the binary can be removed in a
>> post-build script if need be, so remove the option and add it in legacy.
>
> I did a build of openssl on aarch64, and the openssl binary makes up almost 20%
> of the package and 5% of a minimal filesystem (with glibc though). I think
> that's a fairly significant percentage, so I think it's worthwhile to keep this
> option.
>
> Of course, people who care about size should probably use libressl :-)
>
> How does it help for the libssl virtual package? For the engines I can
> understand because other packages select it, but this one could stay, no?
>
> Regards,
> Arnout
Hi Arnout.
It helps in having matching options for both. Regarding engines libressl
doesn't handle that. And in openssl we just remove the tool with that
option - arguably we can do the same with libressl, but then other
people might chime in for adding that same option to some other $package
and we'd get an option overload.
Hence i found the opportunity a good one for cleaning up.
Regards.
prev parent reply other threads:[~2016-01-09 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 12:35 [Buildroot] [PATCH 1/2] openssl: remove binary install option Gustavo Zacarias
2016-01-05 12:35 ` [Buildroot] [PATCH 2/2] openssl: remove additional engines option Gustavo Zacarias
2016-01-08 23:35 ` Arnout Vandecappelle
2016-01-08 23:33 ` [Buildroot] [PATCH 1/2] openssl: remove binary install option Arnout Vandecappelle
2016-01-09 13:13 ` Gustavo Zacarias [this message]
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=56910796.5040204@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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