From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 2/2] package/libapparmor-utils: new package
Date: Fri, 27 Mar 2020 10:09:43 +0100 [thread overview]
Message-ID: <20200327100943.688ea008@windsurf.home> (raw)
In-Reply-To: <20200326225641.15536-2-angelo@amarulasolutions.com>
Hello Angelo,
On Thu, 26 Mar 2020 23:56:41 +0100
Angelo Compagnucci <angelo.compagnucci@gmail.com> wrote:
> diff --git a/package/libapparmor-utils/libapparmor-utils.mk b/package/libapparmor-utils/libapparmor-utils.mk
> new file mode 100644
> index 0000000000..3b2b47be07
> --- /dev/null
> +++ b/package/libapparmor-utils/libapparmor-utils.mk
> @@ -0,0 +1,65 @@
> +################################################################################
> +#
> +# libapparmor-utils
> +#
> +################################################################################
> +
> +LIBAPPARMOR_UTILS_BASE_VERSION = 2.13
> +LIBAPPARMOR_UTILS_VERSION = $(LIBAPPARMOR_UTILS_BASE_VERSION).3
> +LIBAPPARMOR_UTILS_SOURCE = apparmor-$(LIBAPPARMOR_UTILS_VERSION).tar.gz
This is using the same source code as the libapparmor package, so
unless there is a very solid reason for having a separate package (and
it should be explained in the commit log), we prefer in Buildroot to
have one package for one upstream project, so this logic should go into
package/libapparmor/.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-03-27 9:09 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 [this message]
2020-03-27 9:08 ` [Buildroot] [PATCH v3 1/2] package/libapparmor: " Thomas Petazzoni
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=20200327100943.688ea008@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox