Structure of the Repository

The main directories of the AI Repository are as follows: readme.txt This file. ls-Rla.gz The results of doing ls -Rla on the repository. areas/ AI software and other materials organized according to topic or field. copying/ Copies of the GNU GPL and various other copyright notices. doc/ Information related to ftp sites, bitftp, ftpmail, etc. events/ Calendar of events, including conferences, workshops, and other meetings and announcements. file_ext.txt File extensions in use in the repository. html/ Mosaic-related documents, FAQ files, etc. lang/ Programming language implementations, including Lisp, Scheme, and Prolog. ls-Rla.gz The results of running ls -Rla on the repository. ptfai/ Administrative materials related to the AI CD-ROM pubs/ Publications including technical reports, FAQ postings, theses, mailing list archives, etc. util/ Compression and archiving software (gzip, tar, etc.) The repository has standardized on using tar for producing archives of files and gzip for compression. For example, shell archives have been replaced with tar files, and compressed files (.Z) recompressed using GZIP (.gz). GZIP uses the Lempel-Ziv algorithm (LZ77), and generally achieves better compression than LZW (compress), Huffman coding (pack) and adaptive Huffman coding
(compact), and is patent free. Implementations exist for VMS, MSDOS, OS/2, Atari, Unix, and Macintosh; see the util/ directory for copies of the sources.

Packages that are intended solely for use on a PC or Macintosh may be archived using the formats common on those machines, such as zip, sit, cpt, and hqx. The util/ directory contains tools for manipulating these files on other systems.

Due to its size, the repository is split among several disk partitions. So cding to a directory may actually move you to a different partition. Nevertheless, each partition mimics the entire directory structure, so that

   cd .. 
will actually work as expected.

Further information on a package, such as a description of the contents, mailing lists, E-mail addresses for bug reports, and so on, will be included in a file named 0.doc in the package's directory.