From: Patrick Doyle <wpdster@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] python-pip
Date: Tue, 1 May 2018 16:22:34 -0400 [thread overview]
Message-ID: <CAF_dkJC3g+8LOcchfafNMEUUpdBFfpEQJrJVb9RQiR9CKynwxQ@mail.gmail.com> (raw)
What are the chances of (re-?)adding python-pip to buildroot?
I found http://lists.busybox.net/pipermail/buildroot/2013-July/075194.html
where Rohan Fletcher attempted to add it in 2013. But I don't see it
in the 2018.02 branch.
Did folks ask questions, Rohan not reply, and nothing ever came of that?
Yes... I get it... it's not part of the buildroot philosophy to
include package management, but I have a use case that makes sense for
my application.
I can resurrect Rohan's patch, or I can stop now, if somebody else has
a better suggestion for upgrading Python packages on a deployed
system. (I understand that wheels are the new eggs for Python.
Perhaps I should look more carefully at wheels).
I'll go look at/for that now.
--wpd
next reply other threads:[~2018-05-01 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 20:22 Patrick Doyle [this message]
2018-05-02 6:54 ` [Buildroot] python-pip Yegor Yefremov
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=CAF_dkJC3g+8LOcchfafNMEUUpdBFfpEQJrJVb9RQiR9CKynwxQ@mail.gmail.com \
--to=wpdster@gmail.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.