From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Mon, 18 May 2015 16:30:17 +0200 Subject: [Buildroot] [PATCH v5 09/24] busybox: selinux support In-Reply-To: References: <1431553177-7280-1-git-send-email-clayton.shotwell@rockwellcollins.com> <1431553177-7280-10-git-send-email-clayton.shotwell@rockwellcollins.com> Message-ID: <20150518163017.2d87c2a7@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Clayton Shotwell, On Mon, 18 May 2015 09:14:54 -0500, Clayton Shotwell wrote: > >> +config BR2_PACKAGE_BUSYBOX_SELINUX > >> + select BR2_PACKAGE_LIBSELINUX > >> + depends on BR2_TOOLCHAIN_HAS_THREADS > >> + depends on !BR2_STATIC_LIBS > >> + bool "Enable SELinux support" > > Does not this option also need to select > > BR2_PACKAGE_BUSYBOX_INDIVIDUAL_BINARIES? > > Those features are not necessarily dependent, it mostly depends on > what parts of busybox are being used. For instance, if a configuration > only used a couple of minor busybox features, such as simple command > line utilities, the symlinked version of busybox could be used to save > space. If busybox was providing more features, such as crond, then > individual binaries would have to be enabled for the SELinux type > transitions to occur properly. I would like to leave that up to the > individual user to enable the individual binaries as needed. Then exactly this needs to be copy/pasted in the help text of this option :-) Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com