the first that is found will be used in the compilation. The libraries are also written -in Haskell and could be found on Hackage: http://hackage.haskell.org/packages/archive/pkg-list.html. If you want to check whether, +in Haskell and could be found on Hackage: http://hackage.haskell.org/packages/archive/pkg-list.html. If you want to check whether, you already have some of these you can use the following command:
$ ghc-pkg list
-which shows the list of all installed libraries. +which shows the list of all installed libraries.
Haskeline is the easiest to install because it is a pure Haskell library but currently @@ -120,8 +120,9 @@ if you tend to work on non-Latin language. Finaly readline supports both word co and Unicode. Currently this is the best supported library.
-Before to get the GF sources you also need Darcs. Darcs is a decentralized revision control system, -see: http://darcs.net/ for more information. There are precompiled packages for many platforms available at +Before to get the GF sources you also need Darcs, version 2 or later. +Darcs is a decentralized revision control system, +see http://darcs.net/ for more information. There are precompiled packages for many platforms available at http://darcs.net/DarcsWiki/CategoryBinaries. There is also source code if you want to compile it yourself. Darcs is also written in Haskell and so you can use GHC to compile it.
@@ -141,7 +142,7 @@ If you plan to work continuously on GF then you should consider to get read-writ Anyone can get the latest development version of GF by running (all on one line):- $ darcs get --partial --set-scripts-executable http://code.haskell.org/gf/ + $ darcs get --lazy --set-scripts-executable http://code.haskell.org/gf/
@@ -168,7 +169,7 @@ Since every copy is a repository, you can have local version control of your changes.
-If you have added files, you first need to tell your local repository to +If you have added files, you first need to tell your local repository to keep them under revision control:
@@ -198,7 +199,7 @@ repository.Submitting patches
If you are using read-only access, send your patches by email to -someone with write-access. First record your changes in your local +someone with write-access. First record your changes in your local repository, as described above. You can send any number of recorded patches as one patch bundle. You create the patch bundle with:
@@ -223,7 +224,7 @@ patch directly from darcs. If so, replace-o mypatch.patchwithRead-write access
If you have a user account on code.haskell.org, you can get read-write access over SSH -to the GF repository. +to the GF repository. To get an account, fill out this form. Once you have an account, ask <aarne@chalmers.se> to add you to the
@@ -234,11 +235,11 @@ Get your copy with (all on one line), replacingGFproject.bringertwith your own username on code.haskell.org:- $ darcs get --partial --set-scripts-executable bringert@code.haskell.org:/srv/code/gf + $ darcs get --lazy --set-scripts-executable bringert@code.haskell.org:/srv/code/gf-The option
--partialmeans that you do not download all of the +The option--lazymeans that darcs defers downloading all the history for the repository. This saves space, bandwidth and CPU time, and most people don't need the full history of all changes in the past. @@ -261,7 +262,7 @@ Without-a, you can choose which patches you want to get. There are two steps to commiting a change to the main repo. First you have to record the changes that you want to commit, then you push them to the main repo. For instructions on recording your changes locally, -see "Recording local changes" above. Then you can push the patch(es) to +see "Recording local changes" above. Then you can push the patch(es) to the main repo. If you are using ssh-access, all you need to do is:@@ -337,7 +338,7 @@ library after each change. In this case use this extended command: $ runghc Setup.hs build rgl-none-The resource library could also be compiled in two modes: with present tense only and +The resource library could also be compiled in two modes: with present tense only and with all tenses. By default it is compiled with all tenses. If you want to use the library with only present tense you can compile it in this special mode with the command: @@ -455,7 +456,7 @@ GF has testsuite. It is run with the following command:
The testsuite architecture for GF is very simple but still very flexible. GF by itself is an interpreter and could execute commands in batch mode. -This is everything that we need to organize a testsuite. The root of the +This is everything that we need to organize a testsuite. The root of the testsuite is the testsuite/ directory. It contains subdirectories which themself contain GF batch files (with extension .gfs). The above command searches the subdirectories of the testsuite/ directory for files with extension diff --git a/doc/gf-developers.txt b/doc/gf-developers.txt index 5b1e3c819..872d6ef65 100644 --- a/doc/gf-developers.txt +++ b/doc/gf-developers.txt @@ -1,6 +1,6 @@ GF Developers Guide Authors: Björn Bringert and Krasimir Angelov -Last update: %%date(%c) +Last update: %%mtime(%c) % NOTE: this is a txt2tags file. % Create an html file from this file using: @@ -67,8 +67,9 @@ it first. Unfortunately editline does not have good support for Unicode. This wi if you tend to work on non-Latin language. Finaly readline supports both word completion and Unicode. Currently this is the best supported library. -Before to get the GF sources you also need Darcs. Darcs is a decentralized revision control system, -see: http://darcs.net/ for more information. There are precompiled packages for many platforms available at +Before to get the GF sources you also need Darcs, version 2 or later. +Darcs is a decentralized revision control system, +see http://darcs.net/ for more information. There are precompiled packages for many platforms available at http://darcs.net/DarcsWiki/CategoryBinaries. There is also source code if you want to compile it yourself. Darcs is also written in Haskell and so you can use GHC to compile it. @@ -87,7 +88,7 @@ If you plan to work continuously on GF then you should consider to get read-writ Anyone can get the latest development version of GF by running (all on one line): ``` -$ darcs get --partial --set-scripts-executable http://code.haskell.org/gf/ +$ darcs get --lazy --set-scripts-executable http://code.haskell.org/gf/ ``` This will create a directory called ``gf`` in the current @@ -174,10 +175,10 @@ Get your copy with (all on one line), replacing ``bringert`` with your own username on code.haskell.org: ``` -$ darcs get --partial --set-scripts-executable bringert@code.haskell.org:/srv/code/gf +$ darcs get --lazy --set-scripts-executable bringert@code.haskell.org:/srv/code/gf ``` -The option ``--partial`` means that you do not download all of the +The option ``--lazy`` means that darcs defers downloading all the history for the repository. This saves space, bandwidth and CPU time, and most people don't need the full history of all changes in the past.