Check out a copy of the source code (we will need both the common and xml-keyval packages). We assume that you already have CVS installed. In which case, you should be able to execute the following:

[pkb@salsa pkb]$ mkdir $HOME/src
[pkb@salsa pkb]$ cd $HOME/src
[pkb@salsa pkb]$ cvs checkout xml/common xml/keyval > checkout.log
cvs server: Updating xml/common
cvs server: Updating xml/common/data
cvs server: Updating xml/common/docs
cvs server: Updating xml/common/docs/install
cvs server: Updating xml/common/make
cvs server: Updating xml/common/sh
cvs server: Updating xml/common/xsl
cvs server: Updating xml/keyval
cvs server: Updating xml/keyval/dtd
cvs server: Updating xml/keyval/make
cvs server: Updating xml/keyval/sh
cvs server: Updating xml/keyval/test
cvs server: Updating xml/keyval/test/help
cvs server: Updating xml/keyval/test/msgs
cvs server: Updating xml/keyval/xsl
[pkb@salsa src]$

Now that we have checked out the necessary source files, we will use the configure, make and make install commands in the common package to install the supporting XML files required. If the development system is ready to go, it will result in the following:

[pkb@salsa keyval]$ cd $HOME/src/xml/common
[pkb@salsa keyval]$ ./configure
 
Holy cow Batman! It looks like it worked! Use:
 
  make
 
To build, and then:
 
  make install
 
[pkb@salsa keyval]$ make


Build successful - now use: make install
 
[pkb@salsa keyval]$ make install
 
Install was successful. To verify, run:
 
        make test
 
To avoid invocations like: /home/pkb/usr/bin/common2sh, add:
 
        /home/pkb/usr/bin
 
To your PATH - have fun.
 
[pkb@salsa keyval]$ make test
/home/pkb/public_html/common                                         [ok]
[pkb@salsa keyval]$ 

If you are fortunate enough to see the above output, it means your has enough functionality for the basic parts of XML processing, and that we can proceed to install the xml-keyval package.

If you are unfortunate, the configure command will determine that your system is missing something. The output produced should provide some clues as to what needs to be added to your development system. The following demonstrates what Paul saw the first time he ran it on the system known as lizard:

[pkb@salsa keyval]$  cd $GAIBASE/xml/keyval
[pkb@salsa keyval]$  ./configure
***ERROR*** /net/lizard/opt/java1.3/bin/java does not appear to be a 1.4 JVM
  See: http://java.sun.com/j2se/
***ERROR*** could not find class: org.apache.xalan.xslt.Process
  See: http://xml.apache.org/xalan-j/
***ERROR*** could not find class: org.apache.xml.resolver.tools.CatalogResolver
  See: http://xml.apache.org/commons/
***ERROR*** missing necessary components - please fix and re-run
[pkb@salsa keyval]$ 

You will want to read this document in its entirety if you get output similar to the above.

Once the core set of files has been successfully installed, you can move on to installing one the xml-keyval package (or any other XML package that may be added to the repository). The installation of the xml-keyval package is done in a similar manner:

[pkb@salsa keyval]$  cd $HOME/src/xml/keyval
[pkb@salsa keyval]$  ./configure
 
Holy cow Batman! It looks like it worked! Use:
 
  make
 
To build, and then:
 
  make install
 
[pkb@salsa keyval]$  make
System prepared for: make install
[pkb@salsa keyval]$  make install
System prepared for: make install
/bin/cat "/home/pkb/gai/cvs/xml/keyval/cfg/keyval.sh" >> "/home/pkb/usr/bin/keyval2cc"
/bin/cat "/home/pkb/gai/cvs/xml/keyval/sh/support.sh" >> "/home/pkb/usr/bin/keyval2cc"

... Lots more output ...

/bin/cp -p /home/pkb/gai/cvs/xml/keyval/xsl/keyval2java_help.xsl "/home/pkb/usr/share/keyval/xsl/keyval2java_help.xsl"
 
Install was successful. To verify, run:
 
        make test
 
To avoid invocations like: /home/pkb/usr/bin/keyval2sh, add:
 
        /home/pkb/usr/bin
 
To your PATH - have fun.
 
[pkb@salsa keyval]$  make test
/home/pkb/usr/bin                                                    [ok]
/home/pkb/usr/share/keyval/xsl                                       [ok]
/home/pkb/usr/share/keyval/catalog                                   [ok]
/home/pkb/usr/share/keyval/dtd/keyval                                [ok]
/home/pkb/usr/share/keyval/dtd                                       [ok]
/home/pkb/usr/share/keyval                                           [ok]
/home/pkb/usr/bin/keyval2cc                                          [ok]
/home/pkb/usr/bin/keyval2java                                        [ok]
/home/pkb/usr/bin/keyval2sh                                          [ok]

... Lots more output ...

Finished generating files, looking for differences
 
/home/pkb/gai/cvs/xml/keyval/tmp/test/keyval.cc                      [ok]
/home/pkb/gai/cvs/xml/keyval/tmp/test/keyval.hh                      [ok]
/home/pkb/gai/cvs/xml/keyval/tmp/test/keyval.cfg                     [ok]
/home/pkb/gai/cvs/xml/keyval/tmp/test/keyval.m4i                     [ok]
/home/pkb/gai/cvs/xml/keyval/tmp/test/keyval.sh                      [ok]
/home/pkb/gai/cvs/xml/keyval/tmp/test/keyval.sh_m4i                  [ok]
/home/pkb/gai/cvs/xml/keyval/tmp/test/keyval.java                    [ok]
/home/pkb/gai/cvs/xml/keyval/tmp/test/keyvalValuesConfig.java        [ok]
/home/pkb/gai/cvs/xml/keyval/tmp/test/keyvalValuesEditor.java        [ok]
/home/pkb/gai/cvs/xml/keyval/tmp/test/msgs/keyval.properties         [ok]
/home/pkb/gai/cvs/xml/keyval/tmp/test/help/keyval.html               [ok]
 
Whoo-hoo! Unbelievable! It looks like everything is OK.
[pkb@salsa keyval]$ 

The above shows what happens when things work well. If you are fortunate enough to see the above, you whould be able to make use of the xml-keyval programs (keyval2cc, keyval2sh, keyval2java, etc). If there are issues, you will see one or more error messages.