Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 5/5] thrift: new package
Date: Mon, 28 Oct 2013 11:21:22 -0300	[thread overview]
Message-ID: <526E72E2.3030507@zacarias.com.ar> (raw)
In-Reply-To: <OF50AC6C4A.47FC76CF-ON86257C12.004BD3EC-86257C12.004DEECE@rockwellcollins.com>

On 10/28/2013 11:11 AM, Ryan Barnett wrote:

>>>  That it's implicit from openssl is not really relevant - if the
>>> dependency is ever removed from openssl (OK, this will not happen, but
>>> just imagine) then we'd like to keep the correct dependency here.
>>
>> Ok.
>> All the packages that use openssl should be checked though, almost none
>> of them do zlib either (doesn't mean they use it directly, but a good
>> check wouldn't hurt).
> 
> I guess all I really care about is a comment in regards to zlib being 
> built from having dependancy on openssl. I don't always remember these 
> things so just a friendly reminder comment is good enough.

Point is thrift has a hard dependency on zlib right now (regardless of
openssl, for channel compression) so it is a dependency.
It can be built without it and loose the TZlibTransport but really it's
already pulled in by openssl so making it optional is kind of pointless.
What should be checked is the same holding true for other packages that
do use openssl and _maybe_ use zlib as well in a separate fashion which
haven't accounted for it (like thrift).
So the comment itself wouldn't apply, pulling in zlib does (select +
DEPENDENCIES) which is what i'm doing for the next patchset version.
Regards.

      reply	other threads:[~2013-10-28 14:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 12:15 [Buildroot] [PATCH 1/5] libevent: add host variant Gustavo Zacarias
2013-10-25 12:15 ` [Buildroot] [PATCH 2/5] boost: " Gustavo Zacarias
2013-10-25 21:53   ` Ryan Barnett
2013-10-25 22:23     ` Gustavo Zacarias
2013-10-26  2:29       ` Ryan Barnett
2013-10-25 23:21   ` Arnout Vandecappelle
2013-10-25 23:52     ` Gustavo Zacarias
2013-10-25 12:15 ` [Buildroot] [PATCH 3/5] python-thrift: fix cross building Gustavo Zacarias
2013-10-25 21:54   ` Ryan Barnett
2013-10-25 12:15 ` [Buildroot] [PATCH 4/5] python-thrift: bump to version 0.9.1 and switch to apache Gustavo Zacarias
2013-10-25 12:15 ` [Buildroot] [PATCH 5/5] thrift: new package Gustavo Zacarias
2013-10-26  3:12   ` Ryan Barnett
2013-10-26  9:48     ` Gustavo Zacarias
2013-10-28  7:24       ` Arnout Vandecappelle
2013-10-28 11:02         ` Gustavo Zacarias
2013-10-28 14:11           ` Ryan Barnett
2013-10-28 14:21             ` 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=526E72E2.3030507@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