From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/refpolicy: Add option to disable "dontaudit" rules
Date: Wed, 27 Jan 2021 15:40:27 +0100 [thread overview]
Message-ID: <20210127154027.5ed6cb24@bootlin.com> (raw)
In-Reply-To: <161174367527.5198.14305094941308709573@kwain.local>
Hi Antoine, Thomas,
Thanks for the reviews !
On Wed, 27 Jan 2021 11:34:35 +0100
Antoine Tenart <atenart@kernel.org> wrote:
>Quoting Thomas Petazzoni (2021-01-27 11:01:48)
>> On Wed, 27 Jan 2021 10:56:27 +0100
>> Maxime Chevallier <maxime.chevallier@bootlin.com> wrote:
>>
>> > define REFPOLICY_INSTALL_TARGET_CMDS
>> > - $(REFPOLICY_MAKE) -C $(@D) DESTDIR=$(TARGET_DIR) install
>> > + $(REFPOLICY_MAKE) -C $(@D) DESTDIR=$(TARGET_DIR) \
>> > + $(REFPOLICY_EXTRA_MAKE_INSTALL_TARGETS) install
>>
>> That being said, I'm not clear between what the "policy" make target
>> does (invoked in BUILD_CMDS) and what the "enableaudit" make target
>> does.
>
>The 'policy' target generates a policy.conf file (among other things)
>and 'enableaudit' removes lines from this file. While 'enableaudit'
>seems like a configuration step, it is in fact a fixup one.
>
>Maybe a POST_BUILD_HOOK would be better for that?
You're correct, it seems to be a better way to go, I'll send a v2 with
that solution :)
Thanks,
Maxime
>On a side note, there is no dependency between 'enableaudit' and
>'install'. The above change only works because REFPOLICY_MAKE uses
>MAKE1. (We have the same construct in the configuration step).
>
>Antoine
--
Maxime Chevallier, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
prev parent reply other threads:[~2021-01-27 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 9:56 [Buildroot] [PATCH] package/refpolicy: Add option to disable "dontaudit" rules Maxime Chevallier
2021-01-27 10:01 ` Thomas Petazzoni
2021-01-27 10:34 ` Antoine Tenart
2021-01-27 14:40 ` Maxime Chevallier [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=20210127154027.5ed6cb24@bootlin.com \
--to=maxime.chevallier@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