Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [External] Re: [PATCH 09/30] package/musl-fts: new package
Date: Mon, 23 Sep 2019 15:44:59 +0200	[thread overview]
Message-ID: <20190923154459.0df02d82@windsurf> (raw)
In-Reply-To: <CANQCQpY8Y11Xafg5abz+GbkEYQycXxwTtt2GCoz+=gRPq5GWrQ@mail.gmail.com>

On Mon, 23 Sep 2019 08:36:59 -0500
Matthew Weber <matthew.weber@collins.com> wrote:

> I probably won't send a Reviewed by for the other patches individually
> but I did go through them and it looks good.  (Had a few side
> conversations on the host selinux dependency removal for
> policycoreutils and it seems fine)

Thanks!

Speaking of host python dependencies, I'm also wondering about making
the host-python dependency of host-libselinux and libsemanage optional.
Indeed, they are only needed if you want the Python bindings of
libselinux/libsemanage on the host, and you can perfectly fine have a
working SELinux stack without those.

Now the question is what should trigger the build of those Python
bindings. A visible Config.in.host option ? A hidden Config.in.host
option, but then selected by what ? I guess it's mainly host-setools
that needs the Python bindings of host-libselinux. I'm not sure what
uses the Python bindings of host-libsemanage though.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-09-23 13:44 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-22  9:06 [Buildroot] [PATCH 00/30] SELinux improvements Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 01/30] package/policycoreutils: drop host-dbus-glib dependency from host-policycoreutils Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 02/30] package/policycoreutils: drop host-python(3) dependency for host-policycoreutils Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 03/30] package/policycoreutils: drop host-setools dependency from host-policycoreutils Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 04/30] package/policycoreutils: drop ARCH variable Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 05/30] package/policycoreutils: don't pass DESTDIR when building host variant Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 06/30] package/libsemanage: drop dependency on ustr Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 07/30] package/ustr: remove package Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 08/30] package/libsemanage: reformat HOST_LIBSEMANAGE_DEPENDENCIES Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 09/30] package/musl-fts: new package Thomas Petazzoni
2019-09-23 13:12   ` Matthew Weber
2019-09-23 13:33     ` Thomas Petazzoni
2019-09-23 13:36       ` [Buildroot] [External] " Matthew Weber
2019-09-23 13:44         ` Thomas Petazzoni [this message]
2019-10-09 22:31   ` [Buildroot] " Arnout Vandecappelle
2019-10-10  7:05     ` Thomas Petazzoni
2019-10-10 11:22     ` Petr Vorel
2019-09-22  9:06 ` [Buildroot] [PATCH 10/30] package/libselinux: allow building on !glibc using musl-fts Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 11/30] package/busybox: selinux support now available on !glibc configs Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 12/30] package/checkpolicy: " Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 13/30] package/audit: re-enable on musl Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 14/30] package/selinux-python: now available on !glibc configs Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 15/30] package/setools: " Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 16/30] package/android-tools: fastboot now available on !glibc toolchains Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 17/30] package/restorecond: now available on !glibc configs Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 18/30] package/libsemanage: " Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 19/30] package/policycoreutils: " Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 20/30] package/refpolicy: " Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 21/30] package/libselinux: re-enable on ARC Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 22/30] package/setools: " Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 23/30] package/checkpolicy: " Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 24/30] package/selinux-python: re-enable audit2allow " Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 25/30] package/busybox: re-enable SELinux support " Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 26/30] package/restorecond: re-enable " Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 27/30] package/libsemanage: drop !BR2_arc dependency Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 28/30] package/policycoreutils: " Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 29/30] package/refpolicy: " Thomas Petazzoni
2019-09-22  9:06 ` [Buildroot] [PATCH 30/30] package/android-tools: re-enable fastboot on ARC Thomas Petazzoni
2019-09-22 18:09 ` [Buildroot] [PATCH 00/30] SELinux improvements Arnout Vandecappelle
2019-10-09 22:21   ` Arnout Vandecappelle

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=20190923154459.0df02d82@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox