Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot, python{,3}, and pip
Date: Fri, 10 Aug 2018 21:53:21 +0200	[thread overview]
Message-ID: <20180810215321.3b1d840d@windsurf> (raw)
In-Reply-To: <CAF_dkJCw8P3YcUOgsODcrX_YrdYaYfcxriBFs+dxRSRjUrXf+w@mail.gmail.com>

Hello Patrick,

On Fri, 10 Aug 2018 13:11:04 -0400, Patrick Doyle wrote:
> Does anybody have experience using pip on a buildroot generated system?
> 
> Poking around, I have found patches to add a python-pip module, (for
> example http://lists.busybox.net/pipermail/buildroot/2013-July/075194.html)
> but I don't see that in my 2018.02 release.
> 
> I have a severely memory constrained system and have already found that
> 
> # python3 -mensure-pip
> 
> ...will add a "pip" command to my rootfs once I have booted up... but
> sometimes that command fails (apparently depending on the amount of
> free RAM I have, as a first pass diagnosis) and "pip install
> <some_package>" works sometimes, and fails other times, again
> apparently package size/free RAM relatedly.
> 
> So, I might have other system issues to deal with, but in the mean
> time, I thought I would ask why pip isn't available as an option to
> begin with.
> 
> Yes... I get the whole philosophy of "buildroot doesn't support
> package managers".  Is that the primary reason it isn't supported?  Or
> am I setting myself up for failure should I go down the rathole of
> adding support myself?

The bigger question is why do you need python-pip in the first place ?
It goes against the Buildroot principle of reproducible builds. Why
don't you create Buildroot packages for the Python modules that you
need ? The utils/scanpypi script makes this relatively easy for most
Python modules.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com

  parent reply	other threads:[~2018-08-10 19:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-10 17:11 [Buildroot] buildroot, python{,3}, and pip Patrick Doyle
2018-08-10 17:18 ` Matthew Weber
2018-08-10 19:11   ` Patrick Doyle
2018-08-10 19:53 ` Thomas Petazzoni [this message]
2018-08-10 20:56   ` Patrick Doyle

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=20180810215321.3b1d840d@windsurf \
    --to=thomas.petazzoni@bootlin.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