Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] python-setuptools: bumped version to 0.8
Date: Thu, 13 Feb 2014 22:12:44 +0100	[thread overview]
Message-ID: <20140213221244.117882f0@skate> (raw)
In-Reply-To: <1374316034-31973-1-git-send-email-rohfledev@gmail.com>

Dear Rohan Fletcher,

On Sat, 20 Jul 2013 22:27:12 +1200, Rohan Fletcher wrote:
> 
> Signed-off-by: Rohan Fletcher <rohfledev@gmail.com>
> ---
>  package/python-setuptools/python-setuptools.mk | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

I have integrated this patch (after adjusting it to bump to the latest
setuptools version) into a patch series that I posted at:

  http://patchwork.ozlabs.org/patch/260435/

However, regarding your patches 2/3 and 3/3, we discussed during the
Buildroot Developers Meeting, and the general opinion is that we don't
really like tools such as "pip", because they completely circumvent the
Buildroot logic, which has a number of drawbacks:

 * It does not take care of native dependencies, and quite a few Python
   modules have such dependencies.

 * It does not go through the Buildroot download infrastructure, which
   means that "make external-deps", "make source" do not work for the
   Python modules downloaded by pip.

 * It does not integrate with the Buildroot licensing infrastructure,
   which makes it more complicated to maintain an up-to-date list of
   the components installed in the generated system.

For Perl, Fran?ois Perrad has written a script that given a Perl CPAN
package creates all the necessary Buildroot packages. Such an approach
was accepted by the Buildroot developers, and maybe we should look at
having something similar for Python modules.

Best regards,

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

  parent reply	other threads:[~2014-02-13 21:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-20 10:27 [Buildroot] [PATCH 1/3] python-setuptools: bumped version to 0.8 Rohan Fletcher
2013-07-20 10:27 ` [Buildroot] [PATCH 2/3] python: added hidden openssl option to host python Rohan Fletcher
2013-07-20 10:27 ` [Buildroot] [PATCH 3/3] python-pip: new package Rohan Fletcher
2014-02-13 21:12 ` Thomas Petazzoni [this message]
2014-02-13 22:18   ` [Buildroot] [PATCH 1/3] python-setuptools: bumped version to 0.8 Thomas Petazzoni

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=20140213221244.117882f0@skate \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox