From: Gabriel Niebler <gniebler@suse.com>
To: fstests@vger.kernel.org
Cc: Gabriel Niebler <gniebler@suse.com>
Subject: [PATCH 3/4] README: Add command to install required packages on SUSE
Date: Thu, 3 Mar 2022 14:28:03 +0100 [thread overview]
Message-ID: <20220303132804.4151-4-gniebler@suse.com> (raw)
In-Reply-To: <20220303132804.4151-1-gniebler@suse.com>
The README already listed how to install the required packages on other popular
distributions. Since a lot of filesystem development happens on SUSE systems and
both the command as well as the list of packages are slightly different, it only
made sense to include these.
Signed-off-by: Gabriel Niebler <gniebler@suse.com>
---
README | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/README b/README
index 65e7ed7b..657fb2f6 100644
--- a/README
+++ b/README
@@ -18,6 +18,11 @@ _______________________
libcap-devel
(Older distributions may require xfsprogs-qa-devel as well.)
(Note that for RHEL and CentOS, you may need the EPEL repo.)
+ For openSUSE or SUSE Linux Enterprise:
+ sudo zypper install acct automake bc dbench duperemove dump fio \
+ gcc indent libacl-devel libaio-devel libattr-devel libbtrfs-devel \
+ libcap libcap-devel libtool liburing-devel libuuid-devel lvm2 make \
+ quota sqlite3 xfsdump xfsprogs xfsprogs-devel
- run make
- run make install
- create fsgqa test user ("sudo useradd -m fsgqa")
--
2.35.1
next prev parent reply other threads:[~2022-03-03 13:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 13:28 [PATCH 0/4] README: Fix setup, btrfs and distro info Gabriel Niebler
2022-03-03 13:28 ` [PATCH 1/4] README: Fix environment setup quick start Gabriel Niebler
2022-03-03 13:28 ` [PATCH 2/4] README: Adjust and add btrfs testing information Gabriel Niebler
2022-03-03 13:28 ` Gabriel Niebler [this message]
2022-03-03 13:28 ` [PATCH 4/4] README: Fix indentation to be consistent Gabriel Niebler
2022-03-03 23:47 ` [PATCH 0/4] README: Fix setup, btrfs and distro info Dave Chinner
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=20220303132804.4151-4-gniebler@suse.com \
--to=gniebler@suse.com \
--cc=fstests@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