add README, HACKING, and other documentation

4 files changed, 140 insertions, 53 deletions

diff --git a/HACKING b/HACKING
new file mode 100644
index 0000000..ea18feb
--- /dev/null
+++ b/HACKING
@@ -0,0 +1,8 @@
+check docs/README.xhtml for info.  It's a quick edit of the readme for
+the older rvs-0.5.10, but most of it is still valid.
+
+I'll write a real HACKING file later.
+
+~ Luke Shumaker <LukeShu@sbcglobal.net>
+Happy Hacking!
+
diff --git a/Makefile.orig b/Makefile.orig
index 3ea425e..00c3354 100644
--- a/Makefile.orig
+++ b/Makefile.orig
@@ -11,7 +11,6 @@
 
 # Make Dependencies #################################################
 RM = rm -f
-WWW = links2 -width 70 -dump
 INSTALL = install
 
 # Variables ########################################################
@@ -25,9 +24,9 @@ rvs : wrapper core
 
 .SUFFIXES :
 
-#install : wrapper core
-#	$(INSTALL) -m 755 -T out/rvs $(prefix)/$(bindir)/rvs
-#	$(INSTALL) -m 755 -d out/rvs-core $(libdir)/core
+install : wrapper core
+	$(INSTALL) -m 755 -T out/rvs $(prefix)/$(bindir)/rvs
+	$(INSTALL) -m 755 -d out/rvs-core $(libdir)/core
 
 wrapper : lib out/rvs
 
diff --git a/README b/README
new file mode 100644
index 0000000..d208edb
--- /dev/null
+++ b/README
@@ -0,0 +1,72 @@
+//////////////////////////////////////////////////////////////////////
+	rvs - retroactive versioning system
+	                  versioning system that allows you to check
+	                  in commit 2 before commit 1
+//////////////////////////////////////////////////////////////////////
+
+CONTENTS:
+	1 ) Introduction
+	2 ) Building
+	2.1 ) configuration
+
+//////////////////////////////////////////////////////////////////////
+== 1: Introduction
+The name is a little bit of a nod to RCS (revision control system),
+and even less to CVS.  I'm not particularly fond of CVS, but recognize
+it's impact on the scm scene.
+
+rvs is about being able to go back and edit *anything* that has
+already been committed.  Yes, some other SCMs do this, but fuck things
+proper if someone else has a copy of the old version.
+
+Why would you want to do this?  Take for example the Bazaar repository
+rvs is hosted on: It starts at 0.6.0, what if I later want to import
+0.0.0 - 0.5.10?  Or if I'm trying to construct a history of BSD,
+and import all the BSDs I can find, such as 1,3,4, then latter find 2?
+
+== 2: Building
+rvs doesn't exactly use the GNU build system, but acts much like it
+does. To build rvs with default configuration, simply run:
+	$ ./configure
+	$ make
+	# make install
+It's generally considered good practice to build in another directory
+than the source directory, however, this is not the case fo rvs.  In
+fact, it must be build in the source directory.  You needn't be
+worried about it making the source direcotory messy, all source is
+kept in `DIR/source', all finished files in `DIR/out', and all
+temporary build files in `DIR/tmp'.
+
+=== 2.1: Configuration
+There are several configuration variables that can be set. The default
+values are kept in the file `Variables'.
+
+Variables is in the format `VAR_NAME<tab>VALUE'.  You can modify these
+configuration variables by editing the `Variables' file directly, or
+by running ./configure such as:
+	$ ./configure --VAR_NAME=VALUE
+
+The different configuration variables are as follows:
+VER	value='0.6.0'
+	rvs's internal varsion number
+SHELL	value='/usr/bin/env bash'
+	the shell that scripts will be run in.
+prefix	value="$HOME"
+	where the files will be installed.  For me the defualt is
+	`/home/luke'.  Many of you will want to change this to '/usr'
+bindir	value='bin'
+	the binaries folder inside the prefix.  If I leave the prefix
+	and bindir the same, for me rvs is installed in
+	`/home/luke/bin'.  If I change prefix to '/usr', then rvs will
+	be installed in `/usr/bin'
+libdir	value='/etc/rvs/'
+	where the rvs libraries will be installed.
+	in rvs almost nothing is actually done int the core binary
+	([$prefix]/[$bindir]/rvs) but option handling.  All the real
+	work is done in modular sub-programs.  I call them libraries,
+	even though they are independend programs that communicate via
+	pipes.
+
+~ Luke Shumaker <LukeShu@sbcglobal.net>
+Happy Hacking!
+
diff --git a/docs/README.xhtml b/docs/README.xhtml
index 3d6c612..ded2de0 100644
--- a/docs/README.xhtml
+++ b/docs/README.xhtml
@@ -4,48 +4,45 @@
 	"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
 <head>
-	<title>rvs $$VER$$</title>
+	<title>rvs 0.6.0</title>
 	<meta http-equiv="content-type" content="text/html; charset=utf-8"/>
 </head>
+
 <body>
-<h1>rvs $$VER$$</h1>
+<h1>rvs 0.6.0</h1>
 <p>rvs is a basic versioning system I've been writing. If you don't know what that means, it isn't for you (at least not at this stage in development).</p>
 
-<h2>installation</h2>
-<p>After you have obtained the source code, cd into the directory and run:<code>
-<br />./configure
-<br />make install
-</code></p>
-<p>instead of using options to <kbd>./configure</kbd> like <samp>./configure --prefix=/usr/bin</samp>, all configuration options (that effect the installation, not the build process), are stored in the file <kbd>Variables</kbd>. Many of the source files use variables in the form <samp>$$VARNAME$$</samp>. The <kbd>./configure</kbd> script replaces each instance of this with the value defined in <kbd>Variables</kbd>. <kbd>Variables</kbd> contains a variable name, tab character, then value on each line.</p>
+<h2>installation</h2><li><kbd>soruce/rvs-core/commit</kbd></li>
+<p>see <a href="../README"><kbd>README</kbd></a> file</p>
 
 <ul>
-	<li><kbd>/etc/abomination/modules/rvs/commit</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/commit.d</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/commit.f</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/get</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/get.d</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/get.f</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/init</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/lib/rvsdb</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/lib/stdio</kbd></li>
-	<li><kbd>/usr/bin/rvs</kbd></li>
+	<li><kbd>source/rvs-corecommit</kbd></li>
+	<li><kbd>source/rvs-corecommit.d</kbd></li>
+	<li><kbd>source/rvs-corecommit.f</kbd></li>
+	<li><kbd>source/rvs-coreget</kbd></li>
+	<li><kbd>source/rvs-coreget.d</kbd></li>
+	<li><kbd>source/rvs-coreget.f</kbd></li>
+	<li><kbd>source/rvs-coreinit</kbd></li>
+	<li><kbd>source/rvs-corelib/rvsdb</kbd></li>
+	<li><kbd>source/rvs-corelib/stdio</kbd></li>
+	<li><kbd>source/rvs</kbd></li>
 </ul>
 
 <h2>system requirements</h2>
-<p>Pretty much any *nix system should be able to run rvs, provided it has bash, and bash is installed at <kbd>/bin/bash</kbd> (e.g.: <a href="http://www.freebsd.org/">FreeBSD</a> has it at <kbd>/usr/bin/bash</kbd>, so you should set up a symlink). rvs is not designed for Windows, but should be able to run in bash if you have some *nix pack installed.</p>
+<p>Pretty much any *nix system should be able to run rvs, provided it has bash, and bash is installed at <kbd>/bin/bash</kbd> (e.g.: <a href="http:/www.freebsd.org/">FreeBSD</a> has it at <kbd>source/bash</kbd>, so you should set up a symlink). rvs is not designed for Windows, but should be able to run in bash if you have some *nix pack installed.</p>
 <p>To my knowledge, this is the absolute requirements (all need to be in your PATH):</p>
 <ul>
-	<li><a href="http://www.gnu.org/software/bash/">bash</a> (needs to be installed at <kbd>/bin/bash</kbd>)</li>
-	<li>cat      (included in <a href="http://www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
-	<li>cp       (included in <a href="http://www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
-	<li>cut      (included in <a href="http://www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
-	<li>echo     (included in <a href="http://www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
-	<li>mkdir    (included in <a href="http://www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
-	<li>rm       (included in <a href="http://www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
-	<li>sed      (included in <a href="http://www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
-	<li>sha1sum  (included in <a href="http://www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
-	<li>tempfile (included in <a href="http://www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
-	<li>tr       (included in <a href="http://www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
+	<li><a href="http:/www.gnu.org/software/bash/">GNU bash</a></li>
+	<li>cat      (included in <a href="http:/www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
+	<li>cp       (included in <a href="http:/www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
+	<li>cut      (included in <a href="http:/www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
+	<li>echo     (included in <a href="http:/www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
+	<li>mkdir    (included in <a href="http:/www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
+	<li>rm       (included in <a href="http:/www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
+	<li>sed      (included in <a href="http:/www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
+	<li>sha1sum  (included in <a href="http:/www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
+	<li>tempfile (included in <a href="http:/www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
+	<li>tr       (included in <a href="http:/www.gnu.org/software/coreutils/">GNU Core Utils</a>)</li>
 </ul>
 
 <h2>usage</h2>
@@ -57,24 +54,22 @@
 	<dt>check out to the current directory</dt>
 		<dd><kbd>rvs get <var>ID</var></kbd> This checks out commit <var>ID</var></dd>
 </dl>
-<p>The system will bork if you have filenames with spaces or newlines. Why? Because you haven't written a patch to fix it yet.</p>
-<p>Feel free to push to the <a href="https://code.launchpad.net/~lukeshu/+junk/rvs-release">launchpad repository</a>.</p>
 
 <h2>hacking</h2>
-<p>Again, here is a list of all files in <kbd>rvs-0.5.10.tar.gz</kbd>:</p>
+<p>Again, here is a list of all files when you check out</p>
 <ul>
-	<li><kbd>/etc/abomination/modules/rvs/commit</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/commit.d</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/commit.f</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/get</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/get.d</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/get.f</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/init</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/lib/rvsdb</kbd></li>
-	<li><kbd>/etc/abomination/modules/rvs/lib/stdio</kbd></li>
-	<li><kbd>/usr/bin/rvs</kbd></li>
+	<li><kbd>source/rvs-corecommit</kbd></li>
+	<li><kbd>source/rvs-corecommit.d</kbd></li>
+	<li><kbd>source/rvs-corecommit.f</kbd></li>
+	<li><kbd>source/rvs-coreget</kbd></li>
+	<li><kbd>source/rvs-coreget.d</kbd></li>
+	<li><kbd>source/rvs-coreget.f</kbd></li>
+	<li><kbd>source/rvs-coreinit</kbd></li>
+	<li><kbd>source/rvs-corelib/rvsdb</kbd></li>
+	<li><kbd>source/rvs-corelib/stdio</kbd></li>
+	<li><kbd>source/rvs</kbd></li>
 </ul>
-<p>These are all shell scripts and may be modified directly. I have designed this system to be extremely modular. As you may have figured out, each bit on functionality is in it's own script, and <kbd>/usr/bin/rvs</kbd> is just a wrapper for them. If you wish to move the directory with the sub-modules, all you have to do is update the variablle <code><var>RVSDIR</var></code> towards the beginning of <kbd>/usr/bin/rvs</kbd>.</p>
+<p>These are all shell scripts and may be modified directly. I have designed this system to be extremely modular. As you may have figured out, each bit on functionality is in it's own script, and <kbd>source/rvs</kbd> is just a wrapper for them. If you wish to move the directory with the sub-modules after it has been compiled (see variables), all you have to do is update the variablle <code><var>RVSDIR</var></code> towards the beginning of <kbd>source/rvs</kbd>.</p>
 <p><kbd>commit</kbd> actually does take a parameter. It can commit any file or directory. It works as it does because if no file is given, it defaults to <kbd>./</kbd>. If it is given a directory (as it is by default), it loops through each file in the directory and commits them (by calling itself). In order to actually commit a file or directory it calls <code>rvs commit.<var>type</var></code> where <var>type</var> is the standard unix file-type code:</p>
 
 <table>
@@ -84,20 +79,33 @@
 	<tr><td><pre>named <em>p</em>ipe (FIFO)             </pre></td><td>p</td></tr>
 	<tr><td><pre>regular <em>f</em>ile                  </pre></td><td>f</td></tr>
 	<tr><td><pre>symbolic <em>l</em>ink                 </pre></td><td>l</td></tr>
-	<tr><td><pre><em>d</em>ocket                        </pre></td><td>s</td></tr>
+	<tr><td><pre><em>s</em>ocket                        </pre></td><td>s</td></tr>
 	<tr><td><pre><em>d</em>oor (Solaris only)           </pre></td><td>D</td></tr>
 </table>
-<p>As you probably noticed, only directories and regular files have been implemented in this release. <kbd>get</kbd> works in much the same way. If you implement any other file types, save the commit and get functions accordingly, and uncomment the line in <kbd>/etc/abomination/modules/rvs/commit</kbd>. Any commit function takes a filename as an argument and outputs the according commit id to stdout. Any get function takes the commit id as an argument and uses stdout only if verbose, or to report errors. So the modules communicate via pipes, which is generally considered bad-design, and libraries should be used. I deliberatly broke this because this way:</p>
+<p>As you probably noticed, only directories and regular files have been implemented in this release. <kbd>get</kbd> works in much the same way. If you implement any other file types, save the commit and get functions accordingly, and uncomment the line in <kbd>source/rvs-corecommit</kbd>. Any commit function takes a filename as an argument and outputs the according commit id to stdout. Any get function takes the commit id as an argument and uses stdout only if verbose, or to report errors. So the modules communicate via pipes, which is generally considered bad-design, and libraries should be used. I deliberatly broke this because this way:</p>
 <ol>
 	<li>incompatible licences can be used for different modules</li>
 	<li>modules can be added/removed on the fly</li>
 	<li>one can use any lanugage to write new modules, without having to worry about bindings</li>
 </ol>
-
+<h3>build system</h3>
+<p>The build system rvs uses is rather simple.  <kbd>./configure</kbd> does 2 things, create a preprocessor in <kbd>tmp/var.sed</kbd>, and generate a <kbd>Makefile</kbd> with this preprocessor from <a href="../Makefile.orig"><kbd>Makefile.orig</kbd></a>.  Then, the <kbd>Makefile</kbd> (among other things), runs each source file through the preprocessor.</p>
+<h4>preprocessor/variables</h4>
+<p>You know the configuration variables described in <a href="../README"><kbd>README</kbd></a>?  Part of the build process involves running all source files through a pre-processor (kept in <kbd>tmp/var.sed</kbd>).  This preproccessor allows you to reference the configuration variables in any file in <kbd>source/</kbd> or <a href="../Makefile"><kbd>Makefile</kbd></a>.  Any instance of <samp>$$VAR_NAME$$</samp> will be repleced by the value of the variable.</p>
+<h3>known bugs</h3>
+<ul>
+	<li>borks on files with the newline character.  The smart thing to do would be to escape all speacial characters.
+		<br />Files to be changed:<ul>
+			<li><kbd>soruce/rvs-core/commit</kbd></li>
+			<li><kbd>soruce/rvs-core/commit.d</kbd></li>
+			<li><kbd>soruce/rvs-core/get.d</kbd></li>
+		</ul>
+	</li>
+</ul>
 <h3>TODO</h3>
 <ul>
 	<li>implment other unix file types (see above)</li>
-	<li>add real option handling (code from another project is provided in <kbd>/usr/bin/rvs</kbd>)</li>
+	<li>add real option handling (code from another project is provided in <kbd>source/rvs</kbd>)</li>
 	<li>write real documentation</li>
 	<li>implment a parent/child tree<ul>
 		<li>implement branch ids (NOTE: <q>wch</q> should be used to refer to the latest commit in a branch)</li>
@@ -107,7 +115,7 @@
 	<li>usernames/author</li>
 </ul>
 
-<p>I have set up bazaar repository at <a href="https://code.launchpad.net/~lukeshu/+junk/rvs-release">Launchpad</a>. Only until rvs becomes self-hosting.</p>
+<p>I have set up bazaar repository at <a href="https:/launchpad.net/rvs">Launchpad</a>. Only until rvs becomes self-hosting.</p>
 <p>If anyone needs any help, let me know.
 <br />~ Luke Shumaker &lt;<a href="mailto:lukeshu@sbcglobal.net">LukeShu@sbcglobal.net</a>&gt;
 <br />Happy Hacking!</p>