From: Daniel Burgener <dburgener@linux.microsoft.com>
To: selinux@vger.kernel.org
Subject: [PATCH] CONTRIBUTING.md: Drop dependency and build instructions
Date: Mon, 13 Jan 2025 16:38:24 -0500 [thread overview]
Message-ID: <20250113213824.26000-1-dburgener@linux.microsoft.com> (raw)
They are redundant with README.md, and haven't been kept up to date.
For example, the CONTRIBUTING.md dependencies are missing the xmlto
dependency. Rather than try to maintain this information in two places,
just refer contributors to the README and keep the CONTRIBUTING doc
focused on high level process.
Signed-off-by: Daniel Burgener <dburgener@linux.microsoft.com>
---
CONTRIBUTING.md | 9 +--------
1 file changed, 1 insertion(+), 8 deletions(-)
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 7c548e58..e6a677a0 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -23,14 +23,7 @@ using a custom policy please include it as well.
## Compiling
-There are a number of dependencies required to build the userspace
-tools/libraries. On a Fedora system you can install them with yum:
-
- # yum install audit-libs-devel bison bzip2-devel dbus-devel dbus-glib-devel flex flex-devel flex-static glib2-devel libcap-devel libcap-ng-devel pam-devel pcre2-devel python-devel setools-devel swig ustr-devel
-
-The tools and libraries can be built and installed under a private directory from the top level with make, e.g.
-
- $ make DESTDIR=~/obj install install-pywrap
+See README.md for instructions on how to compile and test this project.
## Contributing Code
--
2.34.1
next reply other threads:[~2025-01-13 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-13 21:38 Daniel Burgener [this message]
2025-01-15 15:37 ` [PATCH] CONTRIBUTING.md: Drop dependency and build instructions James Carter
2025-01-16 16:05 ` Petr Lautrbach
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=20250113213824.26000-1-dburgener@linux.microsoft.com \
--to=dburgener@linux.microsoft.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 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.