diff options
Diffstat (limited to 'README')
| -rw-r--r-- | README | 41 |
1 files changed, 21 insertions, 20 deletions
@@ -1,4 +1,3 @@ -#!/bin/less ////////////////////////////////////////////////////////////////////// rvs 0.8c r54 retroactive versioning system @@ -9,22 +8,21 @@ introduction 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. + already been committed. Yes, some other SCMs do this, but get + nasty if someone else has a copy of the old version. - Why would you want to do this? Take for example the Bazaar + 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? + 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? system requirements - Pretty much any *nix system should be able to run rvs. If you - need to use a shell other than /bin/sh, run ./configure with - the --SHELL=YOUR_SHELL option. rvs is not designed for Windows, - but should be able to run in bash if you have some *nix pack - installed. + Pretty much any *nix system should be able to run rvs. If you need + to use a shell other than `/bin/sh`, run `./configure` with the + `--SHELL=YOUR_SHELL` option. rvs is not designed for Windows, but + should be able to run in bash if you have some *nix pack installed. To my knowledge, this is the absolute requirements (all but the shell need to be in your PATH): @@ -42,24 +40,27 @@ system requirements building - rvs doesn't exactly use the GNU build system, but acts much like - it does. To build rvs with default configuration, simply run: + 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. If you would still like to do - this, it can be done in rvs-0.6.1 and up. + directory than the source directory. If you would like to do this, + it can be done in rvs-0.6.1 and up. Configuration - There are several configuration variables that can be set. You can - modify these configuration variables by running ./configure such + There are several configuration variables that can be set. You can + modify these configuration variables by running `./configure` such as: + $ ./configure --VAR_NAME=VALUE The different configuration variables are as follows: + name='rvs' The name of the program. Note that unlike most variables, you should NOT call this in Makefiles @@ -89,6 +90,6 @@ building Where the source code is. The default value evaluates to the directory of the `configure' script. +-- +Happy hacking! ~ Luke Shumaker <LukeShu@sbcglobal.net> -Happy Hacking! - |