From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Python 3 external packages support
Date: Mon, 11 Feb 2013 16:42:31 +0100 [thread overview]
Message-ID: <20130211164231.1baeb62f@skate> (raw)
In-Reply-To: <1360597236.46911.YahooMailNeo@web171802.mail.ir2.yahoo.com>
Dear Patrick,
On Mon, 11 Feb 2013 15:40:36 +0000 (GMT), Patrick wrote:
> Does it sounds accetable to move all the Python related stuff
> (python2, python3 and all python-* packages) to a single directory
> called python ? I know that you would like to have a flat
> arborescence for all packages, but this will help to provide a more
> friendly python menu
The tree of directory is not related to the layout of the menus in
menuconfig/xconfig. So you can perfectly have a flat tree of
directories, and an hierarchical representation of options in
menuconfig/xconfig.
In terms of directories, we prefer a flat solution I believe, even
though it's true some package groups do have their own subdirectory
(for example x11r7).
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-11 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-11 14:54 [Buildroot] [RFC] Python 3 external packages support Patrick
2013-02-11 15:09 ` Thomas Petazzoni
[not found] ` <1360595860.22602.YahooMailNeo@web171805.mail.ir2.yahoo.com>
[not found] ` <20130211162231.0ac06f9c@skate>
2013-02-11 15:40 ` Patrick
2013-02-11 15:42 ` Thomas Petazzoni [this message]
2013-02-11 15:45 ` Samuel Martin
2013-02-11 15:54 ` 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=20130211164231.1baeb62f@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 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.