You can clone with
Cannot retrieve contributors at this time
INSTALLATIONTo install these modules, cd to the directory that contains all of theextracted distribution files, including this INSTALL file, and type thefollowing: perl Makefile.PL make make test make installThe last step probably won't work if you are not the administrator of yourmachine; in that case you either need to get your administrator to installthis for you, or put it in a your own local directory instead.The Makefile.PL can do this for you if you substitute something like thefollowing for the first line above: perl Makefile.PL PREFIX=/tmp/myperl5or: perl Makefile.PL PREFIX=/home/me/myperl5If you are on a Mac system that is older than Mac OS X (Mac OS 9 orearlier) and/or you are otherwise having problems with the Makefile, youcan still install this module the old fashioned way, by copying.Every file in the "lib" folder of this distribution goes in itscorresponding location within the "lib" folder that came with your Perl 5distribution.Or alternately, put them anywhere you want, but you will need to have thatlocation added to your include path by your main program using somethinglike this: use lib '/home/me/myperl5/lib';Then you would want to run the included test programs to make sure themodules are installed correctly. Call them like this for each sequentialt/*.t file: perl t/<file-name>.tAny existing POD is embedded in the module itself. The Makefile probablyextracted it for you in the usual manner, or you can run a POD extractor onit yourself to the same effect. You can also find an HTMLized copy of thePOD on CPAN and other public source archives; I link to one copy of it onmy web site.If the automated 'make test' fails and you want to see more detailsconcerning what went wrong, but you haven't installed the modules yet, thenyou can invoke the following line to see the detailed output of thetest script, which the normal 'make test' usually hides: perl -e "use lib 'blib/lib'; do 't/<file-name>.t';"Use the above line when the problem is something other than the modules notloading in the first place; non-loading should still display the problemunder 'make test'.