[update documentation
John Meacham <john@repetae.net>**20090218112720
 Ignore-this: dbfff88da59670d189f90e599f1fd5a7
] hunk ./docs/building.mkd.in 6
-also under darcs revision control, for information on getting the source code
-from darcs and building it, see the [Development Page](development.shtml).
+also under darcs revision control however the build process from darcs is
+somewhat more involved. For information on getting the source code from darcs
+and building it, see the [Development Page](development.shtml).
hunk ./docs/building.mkd.in 13
-This is by far the easiest way to go about it, an RPM for x86 based systems
-(32 or 64 bits) can be instaled from:
-<http://repetae.net/computer/jhc/drop/@PACKAGE@-@VERSION@-@RPMRELEASE@.i386.rpm>.
+This is by far the easiest way to go about it if you have an rpm based system, an RPM for x86 based systems
+ can be instaled from:
+<http://repetae.net/computer/jhc/drop/@PACKAGE@-@VERSION@-@RPMRELEASE@.x86_64.rpm>.
hunk ./docs/building.mkd.in 25
- * Recent version of [DrIFT](http://repetae.net/computer/haskell/DrIFT)
hunk ./docs/building.mkd.in 50
-
-
-
hunk ./docs/development.mkd 13
+If you simply wish to use jhc, it is easier to build from the distribution
+tarball, as described on the [Building Page](building.shtml). If you are interested
+in developing or modifying jhc itself, then building from darcs as described on this
+page is recommended.
+
hunk ./docs/development.mkd 29
-First you must install darcs, there are a couple projects you need to pull in order to compile jhc, the following should produce a working tree:
+First you must install darcs, there are a couple projects you need to pull in
+order to compile jhc, the following should produce a working tree:
hunk ./docs/development.mkd 52
-however, during development it is often easier to use the raw haskell source of the libraries directly. in order to do that, you can run jhc with the following options when run in the development tree.
+however, during development it is often easier to use the raw haskell source of
+the libraries directly. in order to do that, you can run jhc with the following
+options when run in the development tree.