From: Petr Vorel <pvorel@suse.cz>
To: linux-nfs@vger.kernel.org
Cc: Petr Vorel <pvorel@suse.cz>, "J . Bruce Fields" <bfields@redhat.com>
Subject: [PATCH pynfs 2/2] README: Add openSUSE
Date: Fri, 21 May 2021 08:09:43 +0200 [thread overview]
Message-ID: <20210521060943.7223-2-pvorel@suse.cz> (raw)
In-Reply-To: <20210521060943.7223-1-pvorel@suse.cz>
+ sort alphabetically, improve formatting a bit
Signed-off-by: Petr Vorel <pvorel@suse.cz>
---
README | 12 +++++++++---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git a/README b/README
index 9093236..ddb802a 100644
--- a/README
+++ b/README
@@ -3,11 +3,17 @@ the merge of what were originally two independent projects--initially
the 4.0 pynfs code was all moved into the nfs4.0 directory, but as time
passes we expect to merge the two code bases.
-Install dependent modules; on Fedora:
- yum install krb5-devel python3-devel swig python3-gssapi python3-ply
-on Debian:
+Install dependent modules:
+
+* Debian
apt-get install libkrb5-dev python3-dev swig python3-gssapi python3-ply
+* Fedora
+ yum install krb5-devel python3-devel swig python3-gssapi python3-ply
+
+* openSUSE
+ zypper in install krb5-devel python3-devel swig python3-gssapi python3-ply
+
You can prepare both for use with
./setup.py build
which will create auto-generated files and compile any shared libraries
--
2.31.1
next prev parent reply other threads:[~2021-05-21 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 6:09 [PATCH pynfs 1/2] README: Prefer python3 packages over pip Petr Vorel
2021-05-21 6:09 ` Petr Vorel [this message]
2021-05-21 18:17 ` [PATCH pynfs 2/2] README: Add openSUSE J. Bruce Fields
2021-05-23 19:10 ` Petr Vorel
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=20210521060943.7223-2-pvorel@suse.cz \
--to=pvorel@suse.cz \
--cc=bfields@redhat.com \
--cc=linux-nfs@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