From 9f00e660fae9bede6bb3ca761effb98842c3bd51 Mon Sep 17 00:00:00 2001
From: rocky <rocky@sanchez.(none)>
Date: Sun, 5 Apr 2009 21:00:02 -0400
Subject: [PATCH] Revise installation instructions and add what you need to do
 if you want to develop libcdio

---
 README.develop | 30 ++++++++++++++++++++++++++++++
 README.libcdio | 32 ++++++++++++++++++++++++--------
 2 files changed, 54 insertions(+), 8 deletions(-)
 create mode 100644 README.develop

diff --git a/README.develop b/README.develop
new file mode 100644
index 00000000..8dbdeb16
--- /dev/null
+++ b/README.develop
@@ -0,0 +1,30 @@
+Software you'll need to build a development version libcdio
+  - git
+  - autoconf (which contains programs autoconf and autoreconf)
+  - automake 
+  - m4 (used by autoconf)
+  - texinfo (for building documentation)
+
+This is in addition to the software needed to build starting from a the 
+source tar. See README.libcdio for that additional software.
+
+The source code lives the GNU software repository https://savannah.gnu.org/
+The main page Savannah page is 
+  https://savannah.gnu.org/projects/libcdio/
+
+If you check out the source code, you'll need git installed. See the git
+tab of the libcdio project https://savannah.gnu.org/git/?group=libcdio
+which has an additional link for how to get "git".
+
+One you have git:
+
+   git clone git://git.savannah.gnu.org/libcdio.git   
+
+Change into the libcdio directory that just created and run the "autogen.sh"
+shell script
+
+  cd libcdio
+  sh ./autogen.sh 
+
+Please see README.libcdio and follow those instructions starting at step 3.
+Normally autogen doesn't 
diff --git a/README.libcdio b/README.libcdio
index 8e166401..74221849 100644
--- a/README.libcdio
+++ b/README.libcdio
@@ -1,13 +1,31 @@
-If you check out the source from CVS run
-  ./autogen.sh then follow as below, except you don't need to run 
-  ./configure.
+See README.develop if you plan use the git or development version.
 
-To compile the source:
+0. To compile the source, you'll need a POSIX shell and utilites (sh,
+sed, grep, cat), an ANSI C compiler like gcc, and a POSIX "make"
+program like GNU make. You may also want to have "libtool" installed
+for building portable shared libraries.
+
+1. Uncompress and unpack the source code using for example "tar". Recent
+versions of GNU tar can do this in one step like this:
+  tar -xpf libcdio-*.bz  # or libcdio-*.gz
+
+2. Go into the directory, run "configure" followed by "make":
+
+  cd libcdio-*
+  sh ./configure MAKE=gmake 
+
+3. If step 2 works, Now compile everything:
 
-  ./configure MAKE=gmake 
   make
+
+4. Run the regression tests if you want:
+
   make check
-  make install  # may have to do this as root 
+
+5. Install. If the preceeding steps were successful:
+
+  make install  # you may have to do this as root 
+                # or "sudo make install"
 
 
 If you have problems linking libcdio or libiso9660, see the BSD
@@ -100,5 +118,3 @@ seems to lag behind.
 
 Of late FreeBSD folks have been pretty good about testing new releases
 and reporting problems. 
-
-$Id: README.libcdio,v 1.12 2008/03/22 22:51:30 rocky Exp $