From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 4/4] package/selinux-python: always build sepolgen
Date: Thu, 10 Oct 2019 10:02:16 +0200 [thread overview]
Message-ID: <20191010100216.5ac2606c@windsurf> (raw)
In-Reply-To: <7a945931-ca28-45c1-17ba-6a50f5a192d7@mind.be>
On Thu, 10 Oct 2019 09:56:52 +0200
Arnout Vandecappelle <arnout@mind.be> wrote:
> > As you can see, there's much more than audit2allow and sepolgen in this
> > package, even though those additional things are not installed today.
>
> On the other hand, the way it is now is a bit stupid too...
>
> If we ever add these other options, we could still revert this patch. But
> nobody felt the need to add them in the 5 years that selinux exists in Buildroot...
I discovered how this selinux-python package was organized 2 weeks ago,
while packaging it for OpenWRT. And just like what I did with this 30
patches patch series, which comes from the work I did packaging SELinux
for OpenWRT, it was also on my TODO-list to improve selinux-python in
Buildroot. But as you can imagine, this TODO-list is also filled up
with plenty of other things, so I don't know when I'll get to it.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-10-10 8:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 22:06 [Buildroot] [PATCH 1/4] package/selinux-python: add missing empty line before URL Arnout Vandecappelle
2019-10-09 22:06 ` [Buildroot] [PATCH 2/4] package/selinux-python: remove redundant dependencies Arnout Vandecappelle
2019-10-09 22:06 ` [Buildroot] [PATCH 3/4] package/selinux-python: use ordinary config instead of menuconfig Arnout Vandecappelle
2019-10-09 22:06 ` [Buildroot] [PATCH 4/4] package/selinux-python: always build sepolgen Arnout Vandecappelle
2019-10-10 7:26 ` Thomas Petazzoni
2019-10-10 7:56 ` Arnout Vandecappelle
2019-10-10 8:02 ` 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=20191010100216.5ac2606c@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 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.