The apparmor packages comes with a set of profiles for a class of usual,
mostly server-class programs and daemons.
Even though an embedded device will mostly require custom profiles, the
generic ones may come handy, as they also provide "abstractions", that
can serve as templates for custom profiles.
Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
[yann.morin.1998@free.fr: split off into its own patch]
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
Tested-by: Angelo Compagnucci <angelo@amarulasolutions.com>
endif # BR2_PACKAGE_APPARMOR_UTILS
+config BR2_PACKAGE_APPARMOR_PROFILES
+ bool "profiles"
+ help
+ Installs server-class profiles for a wide range of
+ usual programs and daemons.
+
endif # BR2_PACKAGE_APPARMOR
comment "apparmor needs a toolchain w/ headers >= 3.16, threads, C++"
endif # BR2_PACKAGE_APPARMOR_UTILS
+ifeq ($(BR2_PACKAGE_APPARMOR_PROFILES),y)
+APPARMOR_TOOLS += profiles
+endif
+
define APPARMOR_BUILD_CMDS
$(foreach tool,$(APPARMOR_TOOLS),\
$(TARGET_MAKE_ENV) $(TARGET_CONFIGURE_OPTS) \