selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: selinux@vger.kernel.org
Subject: [PATCH] selinux-testsuite: update the dependencies in README.md
Date: Wed, 27 Nov 2019 09:47:20 -0500	[thread overview]
Message-ID: <157486604069.70468.14139138243381994891.stgit@chester> (raw)

From: Paul Moore <paul@paul-moore.com>

The new kernel module tests added in a68d583c2a70 ("selinux-testsuite:
Add kernel module tests") require the kernel-devel package on Fedora,
make sure we list that in the README.md file.

Signed-off-by: Paul Moore <paul@paul-moore.com>
---
 README.md |    4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index e845df8..4352796 100644
--- a/README.md
+++ b/README.md
@@ -53,6 +53,7 @@ similar dependencies):
 * attr _(tools used by the overlayfs tests)_
 * libbpf-devel _(tools used by the bpf tests)_
 * keyutils-libs-devel _(tools used by the keys tests)_
+* kernel-devel _(used by the kernel module tests)_
 
 On a modern Fedora system you can install these dependencies with the
 following command:
@@ -69,7 +70,8 @@ following command:
 		lksctp-tools-devel \
 		attr \
 		libbpf-devel \
-		keyutils-libs-devel
+		keyutils-libs-devel \
+		kernel-devel
 
 The testsuite requires a pre-existing base policy configuration of SELinux,
 using either the old example policy or the reference policy as the baseline.


             reply	other threads:[~2019-11-27 14:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 14:47 Paul Moore [this message]
2019-11-27 15:21 ` [PATCH] selinux-testsuite: update the dependencies in README.md Ondrej Mosnacek
2019-11-27 15:24   ` Stephen Smalley
2019-11-27 15:39     ` Ondrej Mosnacek
2019-11-27 20:43       ` Paul Moore
2019-11-27 15:22 ` Stephen Smalley
2019-12-02 17:21 ` Stephen Smalley
  -- strict thread matches above, loose matches on Subject: below --
2018-10-03 15:52 Paul Moore

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=157486604069.70468.14139138243381994891.stgit@chester \
    --to=paul@paul-moore.com \
    --cc=selinux@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).