All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] python: enable bzip2 in host variant
Date: Thu, 16 Jun 2016 00:01:31 +0200	[thread overview]
Message-ID: <20160616000131.7f09d903@free-electrons.com> (raw)
In-Reply-To: <1461508789-17644-2-git-send-email-eric.le.bihan.dev@free.fr>

Hello,

On Sun, 24 Apr 2016 16:39:48 +0200, Eric Le Bihan wrote:
> Enable support for bzip2 in Python host variant, so the tarfile module
> works properly.
> 
> Signed-off-by: Eric Le Bihan <eric.le.bihan.dev@free.fr>

Could you give some more details about this? The tarfile module seems
to only import the bz2 module when a bzip2-compressed file is handled.
Is this actually the case with rust?

I am hesitant between applying your patch (and therefore removing
package/nodejs/0.10.45/0001-remove-python-bz2-dependency.patch), or
adding an hidden BR2_HOST_PACKAGE_PYTHON_BZIP2 that the rust package
could select to make sure bzip2 support is built into host-python.

Indeed, host-python is used by numerous packages, and we're trying to
not add too many dependencies to host-python. On the other hand,
building bzip2 is pretty fast, so maybe it's reasonable to add it as a
mandatory dependency of host-python.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2016-06-15 22:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-24 14:39 [Buildroot] [PATCH 0/2] Add support for Rust programming language Eric Le Bihan
2016-04-24 14:39 ` [Buildroot] [PATCH 1/2] python: enable bzip2 in host variant Eric Le Bihan
2016-06-15 22:01   ` Thomas Petazzoni [this message]
2016-06-16 20:43     ` Eric Le Bihan
2016-06-16 20:55       ` Thomas Petazzoni
2016-04-24 14:39 ` [Buildroot] [PATCH 2/2] rust: new package Eric Le Bihan
2016-06-15 22:09   ` Thomas Petazzoni
2016-06-15 22:42     ` Charles Hardin
2016-06-16 20:31       ` Eric Le Bihan
2016-06-16 20:25     ` Eric Le Bihan

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=20160616000131.7f09d903@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --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 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.