linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Augusto Mecking Caringi <augustocaringi@gmail.com>
To: linux-btrfs@vger.kernel.org
Cc: Augusto Mecking Caringi <augustocaringi@gmail.com>
Subject: [PATCH] Add more detailed package dependency information to INSTALL file
Date: Sat, 31 May 2014 03:24:46 -0300	[thread overview]
Message-ID: <1401517486-26769-1-git-send-email-augustocaringi@gmail.com> (raw)

Signed-off-by: Augusto Mecking Caringi <augustocaringi@gmail.com>
---
 INSTALL |   13 ++++++++++---
 1 file changed, 10 insertions(+), 3 deletions(-)

diff --git a/INSTALL b/INSTALL
index 8ead607..9a4ab64 100644
--- a/INSTALL
+++ b/INSTALL
@@ -12,9 +12,16 @@ complete:
 modprobe libcrc32c
 insmod btrfs.ko
 
-The Btrfs utility programs require libuuid to build.  This can be found
-in the e2fsprogs sources, and is usually available as libuuid or
-e2fsprogs-devel from various distros.
+The Btrfs utility programs require the following libraries/tools to build:
+
+- libuuid (This can be found in the e2fsprogs sources, and is usually available
+  as libuuid or e2fsprogs-devel from various distros).
+- libattr (Extended attribute library - Development files)
+- libblkid (Block device id library - Development files)
+- liblzo2 (LZO data compression library - Development files)
+- libacl (Access control list library - Development files)
+- e2fslibs (ext2/ext3/ext4 file system libraries - Development files)
+- asciidoc (Text document format tool - For documentation)
 
 Building the utilities is just make ; make install.  The programs go
 into /usr/local/bin.  The mains commands available are:
-- 
1.7.10.4


             reply	other threads:[~2014-05-31  6:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31  6:24 Augusto Mecking Caringi [this message]
2015-02-27 16:53 ` [PATCH] Add more detailed package dependency information to INSTALL file David Sterba

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=1401517486-26769-1-git-send-email-augustocaringi@gmail.com \
    --to=augustocaringi@gmail.com \
    --cc=linux-btrfs@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).