This file is not yet operational. Eventually it should record all changes.
-Till then, you are advised to resort to our CVS server where all changes are
+Till then, you are advised to resort to our git server where all changes are
logged. This is how to get anonymous read-only access:
-$ cvs -d :pserver:anoncvs@cvs.ginac.de:/home/cvs/GiNaC login
-enter the password `anoncvs'
-$ cvs -d :pserver:anoncvs@cvs.ginac.de:/home/cvs/GiNaC -z 9 co GiNaC
+$ git clone git://www.ginac.de/ginac.git ginac
+$ cd ginac; git whatchanged
+Alternatively you can browse the repository on-line at
+http://www.ginac.de/ginac.git
- GCC 2.96 or earlier because proper exception and standard library support
is missing there.
-If you install from CVS, you also need GNU autoconf (>=2.59), automake (>=1.7),
+If you install from git, you also need GNU autoconf (>=2.59), automake (>=1.7),
libtool (>= 1.5), bison (>= 2.3), flex (>= 2.5.33) to be installed.
make check | ~8m | ~12m | largely due to compilation
-To install from CVS
+To install from git
===================
First, download the code:
-
- $ cvs -d :pserver:anoncvs@cvs.ginac.de:/home/cvs/GiNaC login
- [enter "anoncvs" as the password]
- $ cvs -d :pserver:anoncvs@cvs.ginac.de:/home/cvs/GiNaC co GiNaC
- $ cd GiNaC
+ $ git clone git://www.ginac.de/ginac.git ginac
+ $ cd ginac
Secondly, make sure all required software is installed. This is *really*
important step. If some package is missing, the `configure' script might
warning levels. If omitted, it defaults to @option{-g
-O2}.@footnote{The @command{configure} script is itself generated from
the file @file{configure.ac}. It is only distributed in packaged
-releases of GiNaC. If you got the naked sources, e.g. from CVS, you
+releases of GiNaC. If you got the naked sources, e.g. from git, you
must generate @command{configure} along with the various
@file{Makefile.in} by using the @command{autoreconf} utility. This will
require a fair amount of support from your local toolchain, though.}