From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/2] package/libapparmor: new package
Date: Fri, 27 Mar 2020 10:08:30 +0100 [thread overview]
Message-ID: <20200327100830.68e39b50@windsurf.home> (raw)
In-Reply-To: <20200326225641.15536-1-angelo@amarulasolutions.com>
Hello,
On Thu, 26 Mar 2020 23:56:40 +0100
Angelo Compagnucci <angelo.compagnucci@gmail.com> wrote:
> This patch adds libapparmor and its mandatory tools.
>
> * The first step is to compile libraries/libapparmor using the autotools
> infrastructure. Autoreconf is needed due to the attached patches.
> Libapparmor library needs to be installed in staging directory before
> compiling the rest of the tools.
> * The second step is to compile the mandatory parser and binutils
> sub directories, this is done in POST_INSTALL_STAGING_HOOKS.
> * If python3 is available, swig bindings are compiled.
> * parser/apparmor.systemd is actually a systemv init script
> * All Apparmor kernel code is now upstream, so no other patches are
> needed.
>
> Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com>
What are the changes between versions? I.e, what does this v3 changes
compared to v2 ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-03-27 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 22:56 [Buildroot] [PATCH v3 1/2] package/libapparmor: new package Angelo Compagnucci
2020-03-26 22:56 ` [Buildroot] [PATCH v3 2/2] package/libapparmor-utils: " Angelo Compagnucci
2020-03-27 9:09 ` Thomas Petazzoni
2020-03-27 9:08 ` 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=20200327100830.68e39b50@windsurf.home \
--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.