From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] python: select vs depends on
Date: Fri, 10 Jan 2014 15:42:18 +0800 [thread overview]
Message-ID: <20140110154218.6d94ca2c@skate> (raw)
In-Reply-To: <CAAXf6LWjtJzLPxrfET-Wd8661_21QfddOXv1B27uL48BK-o2Kg@mail.gmail.com>
Dear Thomas De Schampheleire,
On Fri, 10 Jan 2014 07:44:50 +0100, Thomas De Schampheleire wrote:
> > For what it's worth, I added in menuconfig options to all of the SELinux
> > packages to specifically enable the Python bindings. When that option is
> > enabled, Python is selected. Doing it this was way chosen after several
> > conversations with Thomas P. about the issue.
>
> Ah, interesting!
> So Thomas, what do you have to say for yourself? ;-)
In the SELinux libraries, the Python stuff is only used when you want
to *debug* SELinux (i.e tune your SELinux policy). Therefore, it is
unlikely that you will need all these SELinux Python bindings on a
final production system. Therefore, it didn't seem appropriate to
enable them automatically when Python is enabled: you may well want to
have Python *and* SELinux on a system, but necessarily have all the
Python bindings of these SELinux libraries, since those are only needed
for debugging purposes.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-01-10 7:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-24 17:14 [Buildroot] [RFC] python: select vs depends on Thomas De Schampheleire
2013-12-24 17:28 ` Yann E. MORIN
2013-12-25 18:42 ` Thomas De Schampheleire
2014-01-09 7:14 ` Arnout Vandecappelle
2014-01-09 14:21 ` Clayton Shotwell
2014-01-10 6:44 ` Thomas De Schampheleire
2014-01-10 7:42 ` Thomas Petazzoni [this message]
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=20140110154218.6d94ca2c@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