[gnome-commander] Updates README.in for development packages

[Uwe Scholz <uwescholz src gnome org>]

commit a1f55b6017fbdcffa9151803e0501eb3811dc14a
Author: Uwe Scholz <uwescholz src gnome org>
Date:   Sun May 21 22:25:01 2017 +0200

    Updates README.in for development packages

 README.in |   12 ++++++++++--
 1 files changed, 10 insertions(+), 2 deletions(-)
---
diff --git a/README.in b/README.in
index fc928ab..4f6ed45 100644
--- a/README.in
+++ b/README.in
@@ -68,8 +68,8 @@ Plugins:
 3. Building
 --------------------------------
 
-GNOME Commander requires glib >= @GLIB_REQ@, GTK+ >= @GTK_REQ@, gnome >= @GNOMEUI_REQ@, 
-gnome-keyring >= @GNOME_KEYRING_REQ@ and unique >= @UNIQUE_REQ@ libraries.
+GNOME Commander requires glib >= @GLIB_REQ@, GTK+ >= @GTK_REQ@, gnome >= @GNOMEUI_REQ@
+and gnome-keyring >= @GNOME_KEYRING_REQ@ libraries.
 
 Additionally GNOME Commander may require:
 
@@ -79,6 +79,9 @@ Additionally GNOME Commander may require:
     its visible directories even when files are create/deleted or changed by
     other programs.
 
+  * unique >= @UNIQUE_REQ@
+    Optional - for uniqueness support: only one running instance at a time
+
   * python >= @PYTHON_REQ@
     Optional - for python plugins support.
 
@@ -94,6 +97,11 @@ Additionally GNOME Commander may require:
   * poppler >= @POPPLER_REQ@
     Optional - for PDF support.
 
+If you install GNOME Commander by manually compiling the sources, keep in
+mind that on most Linux distributions you have to install the development
+packages for the above libraries to be found by the configure script.
+These packages are normaly indicated by a "-dev" or "-devel" suffix,
+e.g. libgnome-dev, taglib-dev, etc.
 
 Simple install procedure: