2
0

README.PERL 4.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118
  1. TOC
  2. ===
  3. - Notes on Perl
  4. - Notes on Perl on Windows
  5. - Notes on Perl modules we use
  6. - Notes on installing a perl module
  7. Notes on Perl
  8. -------------
  9. For our scripts, we rely quite a bit on Perl, and increasingly on
  10. some core Perl modules. These Perl modules are part of the Perl
  11. source, so if you build Perl on your own, you should be set.
  12. However, if you install Perl as binary packages, the outcome might
  13. differ, and you may have to check that you do get the core modules
  14. installed properly. We do not claim to know them all, but experience
  15. has told us the following:
  16. - on Linux distributions based on Debian, the package 'perl' will
  17. install the core Perl modules as well, so you will be fine.
  18. - on Linux distributions based on RPMs, you will need to install
  19. 'perl-core' rather than just 'perl'.
  20. You MUST have at least Perl version 5.10.0 installed. This minimum
  21. requirement is due to our use of regexp backslash sequence \R among
  22. other features that didn't exist in core Perl before that version.
  23. Notes on Perl on Windows
  24. ------------------------
  25. If you will build on Cygwin (and possibly some other POSIX layers),
  26. Perl is already part of your distribution. Simply use the Cygwin
  27. package manager to make sure Perl gets installed.
  28. Otherwise, you will need to install Perl separately. The Perl
  29. package that we know of is ActiveState Perl, available from
  30. http://www.activestate.com/ActivePerl.
  31. Notes on Perl on VMS
  32. --------------------
  33. You will need to install Perl separately. One way to do so is to
  34. download the source from http://perl.org/, unpacking it, reading
  35. README.vms and follow instructions. Another way is to download a
  36. .PCSI file from http://www.vmsperl.com/ and install it using the
  37. POLYCENTER install tool.
  38. Notes on Perl modules we use
  39. ----------------------------
  40. We make increasing use of Perl modules, and do our best to limit
  41. ourselves to core Perl modules to keep the requirements down. There
  42. are just a few exceptions:
  43. Test::More We require the minimum version to be 0.96, which
  44. appeared in Perl 5.13.4, because that version was
  45. the first to have all the features we're using.
  46. This module is required for testing only! If you
  47. don't plan on running the tests, you don't need to
  48. bother with this one.
  49. Text::Template This module is not part of the core Perl modules.
  50. As a matter of fact, the core Perl modules do not
  51. include any templating module to date.
  52. This module is absolutely needed, configuration
  53. depends on it.
  54. To avoid unnecessary initial hurdles, we have bundled a copy of the
  55. following modules in our source. They will work as fallbacks if
  56. these modules aren't already installed on the system.
  57. Text::Template
  58. Notes on installing a perl module
  59. ---------------------------------
  60. There are a number of ways to install a perl module. In all
  61. descriptions below, Text::Template will server as an example.
  62. 1. for Linux users, the easiest is to install with the use of your
  63. favorite package manager. Usually, all you need to do is search
  64. for the module name and to install the package that comes up.
  65. On Debian based Linux distributions, it would go like this:
  66. $ apt-cache search Text::Template
  67. ...
  68. libtext-template-perl - perl module to process text templates
  69. $ sudo apt-get install libtext-template-perl
  70. Perl modules in Debian based distributions use package names like
  71. the name of the module in question, with "lib" prepended and
  72. "-perl" appended.
  73. 2. Install using CPAN. This is very easy, but usually requires root
  74. access:
  75. $ cpan -i Text::Template
  76. Note that this runs all the tests that the module to be install
  77. comes with. This is usually a smooth operation, but there are
  78. platforms where a failure is indicate even though the actual tests
  79. were successful. Should that happen, you can force an
  80. installation regardless (that should be safe since you've already
  81. seen the tests succeed!):
  82. $ cpan -f -i Text::Template
  83. Note: on VMS, you must quote any argument that contains upper case
  84. characters, so the lines above would be:
  85. $ cpan -i "Text::Template"
  86. and:
  87. $ cpan -f -i "Text::Template"