Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Adam Duskett <adam.duskett@amarulasolutions.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/pkg-generic: Auto-install selinux modules only for upstream refpolicy
Date: Thu, 09 Nov 2023 10:47:24 +0100	[thread overview]
Message-ID: <87h6lvp8b7.fsf@48ers.dk> (raw)
In-Reply-To: <20231009161817.2832969-1-adam.duskett@amarulasolutions.com> (Adam Duskett's message of "Mon, 9 Oct 2023 18:18:17 +0200")

>>>>> "Adam" == Adam Duskett <adam.duskett@amarulasolutions.com> writes:

 > The description of REFPOLICY_CUSTOM_GIT states:
 > The custom refpolicy must define the full policy explicitly,
 > and must be a fork of the original refpolicy, to have the
 > same build system.  When this is selected, only the custom
 > policy definition are taken into account and all the modules
 > of the policy are built into the binary policy.

 > Currently, if a user definess their own policy, a package containing a selinux
 > directory would add to their custom policy, which is not what they would want.
 > Disable applying selinux policies in selinux/ directories for custom git
 > refpolicies.

 > Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>

Committed to 2023.02.x and 2023.08.x, thanks.

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2023-11-09  9:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 16:18 [Buildroot] [PATCH 1/1] package/pkg-generic: Auto-install selinux modules only for upstream refpolicy Adam Duskett
2023-11-04 17:35 ` Thomas Petazzoni via buildroot
2023-11-09  9:47 ` Peter Korsgaard [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=87h6lvp8b7.fsf@48ers.dk \
    --to=peter@korsgaard.com \
    --cc=adam.duskett@amarulasolutions.com \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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