From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] openssl: use git formatted patches
Date: Tue, 21 Jul 2015 10:05:14 -0300 [thread overview]
Message-ID: <55AE438A.1030908@zacarias.com.ar> (raw)
In-Reply-To: <20150720160710.4707d820@free-electrons.com>
On 20/07/15 11:07, Thomas Petazzoni wrote:
Hi Thomas.
> Since you are the de-facto maintainer of the OpenSSL package, could you
> give your opinion about the two patches in this series. I believe PATCH
> 1/2 is OK, but what do you think about PATCH 2/2 ?
It looks fine, however it needs a small refresh (c_rehash was fixed
upstream, hence gone).
> Back in November 2014, Bernd also submitted some patches to enable
> parallel build of OpenSSL, see
> http://lists.busybox.net/pipermail/buildroot/2014-November/112183.html.
> Peter and I rejected them because they were a bit big. My proposal
> relies on downloading Gentoo patches instead, but I don't now if it's
> really any better, since those patches may cause some problems in the
> future to bump OpenSSL.
>
> What do you think? Should we simply wait for OpenSSL upstream to see
> the light and support parallel build?
I don't expect build patches to change much among what are usually
security bumps, and also gentoo has a history of being fast updating
openssl.
I wouldn't hold my breath expecting openssl upstream to fix anything
soon, example patch we have:
http://rt.openssl.org/Ticket/Display.html?id=2770&user=guest&pass=guest
And my personal history with sending patches to them (c_rehash being one
of the cases BTW) vouches for that. If you send it to the RT it may get
"lost" for whatever reason, if you send the patch to the openssl-dev
mailing list it gets ignored.
So +1 from me, openssl is one of those builds you see building and yawn
about.
If it becomes an obstacle to a security bump we can just roll back to
$(MAKE1) until a new patchset arrives.
Regards.
next prev parent reply other threads:[~2015-07-21 13:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-16 19:04 [Buildroot] [PATCH 1/2] openssl: use git formatted patches Thomas Petazzoni
2015-05-16 19:04 ` [Buildroot] [PATCH 2/2] openssl: enable parallel build and installation Thomas Petazzoni
2015-07-20 14:07 ` [Buildroot] [PATCH 1/2] openssl: use git formatted patches Thomas Petazzoni
2015-07-21 13:05 ` Gustavo Zacarias [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-15 3:59 [Buildroot] [PATCH 0/2] openssl parallel build Ryan Barnett
2015-09-15 3:59 ` [Buildroot] [PATCH 1/2] openssl: use git formatted patches Ryan Barnett
2015-09-15 16:47 ` Arnout Vandecappelle
2015-09-15 19:44 ` Ryan Barnett
2015-09-15 20:39 ` Arnout Vandecappelle
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=55AE438A.1030908@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