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] [RFC] Python packages
Date: Wed, 14 Dec 2011 08:46:39 +0100	[thread overview]
Message-ID: <20111214084639.2a76f2bc@skate> (raw)
In-Reply-To: <4EE85335.9060109@visionsystems.de>

Hello,

Le Wed, 14 Dec 2011 08:41:41 +0100,
Yegor Yefremov <yegor_sub1@visionsystems.de> a ?crit :

> I just wanted to add some network related python packages (dpkt and
> netifaces) to buildroot. At the moment we have only pyserial as
> external python component,

And python-mad, in package/multimedia/

> residing in packages/python-serial. Should I pack these packages just
> under Libraries->Networking or should I create special folder
> packages/python-addons and put those packages there?

Your question is strange because you're comparing a location in
menuconfig ("Libraries->Networking") and a location in the source tree
("packages/python-addons") while the two are not related.

From a source tree location perspective, Peter's wish is to keep
everything directly under package/ as much as possible. So we would
have there python/, python-serial/, python-something/,
python-somethingelse/ and so forth. But I think they should all start
with the python- prefix. This wasn't done with Lua extensions and I am
personally not happy with this.

Now, for the location in menuconfig, I must say I don't know. Should we
sort them by Language (Python extensions, Lua extensions) or by usage
type (Network, Multimedia, etc.). So far, the extensions are listed "by
usage", along with all other libraries for the same type of usage.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2011-12-14  7:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14  7:41 [Buildroot] [RFC] Python packages Yegor Yefremov
2011-12-14  7:46 ` Thomas Petazzoni [this message]
2011-12-14  7:59   ` Yegor Yefremov
2011-12-14  8:01   ` Thomas De Schampheleire
2011-12-14  8:34     ` 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=20111214084639.2a76f2bc@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