Download the cTI System

From this page you will be able to access the cTI's sources in a variety of different ways: choose the method that better suits your needs.
We currently offer full sources in gzipped and bzipped tar archive formats, as well as ZIP archives. These are available both from FTP and HTTP servers.

For those concerned with security, we provide ways to verify the authenticity of the packages.

You can also access the sources using CVS: we provide both read-only anonymous access and authenticated read-write access for recognized developers. In addition, we host a Web interface to the CVS repository that is easy to use and comes in handy if you want to browse the sources and see how they evolve.

Finally, you can obtain a mirror of the cTI CVS repository and various other cTI-related data through our anonymous rsync access.


In order to use cTI you should have the following tools and libraries installed on your system:

If you want to port cTI to other Prolog systems we will be glad to work with you in order to fix the problems that may arise.

FTP Access

Check the README* files for additional information.

HTTP Access

With this method you can access the same files as with FTP.

Notes for Non-Experts

Package Verification

For security, the distributed packages are fingerprinted with md5sum and digitally signed with
GPG, the GNU Privacy Guard. The digital signature is by "Roberto Bagnara <bagnara@cs.unipr.it>", whose public key can be found at
You may import the key into your keyring by saving it in a file, and then issuing the command
gpg --import <key-file>

Verifying Files

In our distribution areas, a file called filename.sign contains the digital signature for filename. In order to verify the signature you can issue the command
gpg --verify filename.sign filename
For those only wishing to verify that files have not been corrupted or tampered with, we also provide files called MD5SUMS containing MD5 fingerprints. The contents of these files is something like
150b6e9bc68b25923d32247031447e0d  filename1
5a46c39de027a658c15ed03a7c308e81  filename2
e82a866bb00edf31b2282747354f459c  filename3
You may check the fingerprint of, say, filename2 by issuing the command
md5sum filename2
and making sure the output is
5a46c39de027a658c15ed03a7c308e81  filename2
Alternatively, you may check the fingerprints of several files at once with the command
md5sum --check MD5SUMS
possibly ignoring the errors concerning the files you did not download. For example, if you downloaded filename1 and filename2 but not filename3, everything is fine if your output is something like
filename1: OK
filename2: OK
md5sum: filename3: No such file or directory
filename3: FAILED open or read
md5sum: WARNING: 1 of 3 listed files could not be read
Contrast this with the situation where filename3 exists but is corrupted. Expect your output to look like
filename1: OK
filename2: OK
filename3: FAILED
md5sum: WARNING: 1 of 3 computed checksums did NOT match

Handling .bz2 Files

The .bz2 extension belongs to the
bzip2 compression utility (the successor of good old gzip). You may unpack file.tar.bz2 directly using the commands
tar xjf file.tar.bz2
(new versions of tar), or
tar xIf file.tar.bz2
(older versions of tar), or
bzip2 -c file.tar.bz2 | tar xf -
(all versions of tar).

[Page last updated on January 18, 2013, 10:08:09.]

© Fred Mesnard

Home | Download