| 1 | |
| 2 | Perl Kit, Version 5.0 |
| 3 | |
| 4 | Copyright 1989-1999, Larry Wall |
| 5 | All rights reserved. |
| 6 | |
| 7 | This program is free software; you can redistribute it and/or modify |
| 8 | it under the terms of either: |
| 9 | |
| 10 | a) the GNU General Public License as published by the Free |
| 11 | Software Foundation; either version 1, or (at your option) any |
| 12 | later version, or |
| 13 | |
| 14 | b) the "Artistic License" which comes with this Kit. |
| 15 | |
| 16 | This program is distributed in the hope that it will be useful, |
| 17 | but WITHOUT ANY WARRANTY; without even the implied warranty of |
| 18 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See either |
| 19 | the GNU General Public License or the Artistic License for more details. |
| 20 | |
| 21 | You should have received a copy of the Artistic License with this |
| 22 | Kit, in the file named "Artistic". If not, I'll be glad to provide one. |
| 23 | |
| 24 | You should also have received a copy of the GNU General Public License |
| 25 | along with this program; if not, write to the Free Software Foundation, |
| 26 | Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA. |
| 27 | |
| 28 | For those of you that choose to use the GNU General Public License, |
| 29 | my interpretation of the GNU General Public License is that no Perl |
| 30 | script falls under the terms of the GPL unless you explicitly put |
| 31 | said script under the terms of the GPL yourself. Furthermore, any |
| 32 | object code linked with perl does not automatically fall under the |
| 33 | terms of the GPL, provided such object code only adds definitions |
| 34 | of subroutines and variables, and does not otherwise impair the |
| 35 | resulting interpreter from executing any standard Perl script. I |
| 36 | consider linking in C subroutines in this manner to be the moral |
| 37 | equivalent of defining subroutines in the Perl language itself. You |
| 38 | may sell such an object file as proprietary provided that you provide |
| 39 | or offer to provide the Perl source, as specified by the GNU General |
| 40 | Public License. (This is merely an alternate way of specifying input |
| 41 | to the program.) You may also sell a binary produced by the dumping of |
| 42 | a running Perl script that belongs to you, provided that you provide or |
| 43 | offer to provide the Perl source as specified by the GPL. (The |
| 44 | fact that a Perl interpreter and your code are in the same binary file |
| 45 | is, in this case, a form of mere aggregation.) This is my interpretation |
| 46 | of the GPL. If you still have concerns or difficulties understanding |
| 47 | my intent, feel free to contact me. Of course, the Artistic License |
| 48 | spells all this out for your protection, so you may prefer to use that. |
| 49 | |
| 50 | -------------------------------------------------------------------------- |
| 51 | |
| 52 | Perl is a language that combines some of the features of C, sed, awk |
| 53 | and shell. See the manual page for more hype. There are also two Nutshell |
| 54 | Handbooks published by O'Reilly & Assoc. See pod/perlbook.pod |
| 55 | for more information. |
| 56 | |
| 57 | Please read all the directions below before you proceed any further, and |
| 58 | then follow them carefully. |
| 59 | |
| 60 | After you have unpacked your kit, you should have all the files listed |
| 61 | in MANIFEST. |
| 62 | |
| 63 | Installation |
| 64 | |
| 65 | 1) Detailed instructions are in the file INSTALL which you should read. |
| 66 | In brief, the following should work on most systems: |
| 67 | |
| 68 | rm -f config.sh Policy.sh |
| 69 | sh Configure -de |
| 70 | make |
| 71 | make test |
| 72 | make install |
| 73 | |
| 74 | For most systems, it should be safe to accept all the Configure defaults. |
| 75 | It is recommended that you accept the defaults the first time you build |
| 76 | or if you have any problems building. |
| 77 | |
| 78 | The above commands will install Perl to /usr/local or /opt, depending |
| 79 | on the platform. If that's not okay with you, use |
| 80 | |
| 81 | rm -f config.sh Policy.sh |
| 82 | sh Configure |
| 83 | make |
| 84 | make test |
| 85 | make install |
| 86 | |
| 87 | Full configuration instructions can be found in the INSTALL file. |
| 88 | |
| 89 | 2) Read the manual entries before running perl. |
| 90 | |
| 91 | 3) IMPORTANT! Help save the world! Communicate any problems and suggested |
| 92 | patches to perlbug@perl.com so we can keep the world in sync. |
| 93 | If you have a problem, there's someone else out there who either has had |
| 94 | or will have the same problem. It's usually helpful if you send the |
| 95 | output of the "myconfig" script in the main perl directory. |
| 96 | |
| 97 | If you've succeeded in compiling perl, the perlbug script in the utils/ |
| 98 | subdirectory can be used to help mail in a bug report. |
| 99 | |
| 100 | If possible, send in patches such that the patch program will apply them. |
| 101 | Context diffs are the best, then normal diffs. Don't send ed scripts-- |
| 102 | I've probably changed my copy since the version you have. |
| 103 | |
| 104 | Watch for perl patches in comp.lang.perl.announce. Patches will generally |
| 105 | be in a form usable by the patch program. If you are just now bringing |
| 106 | up perl and aren't sure how many patches there are, write to me and I'll |
| 107 | send any you don't have. Your current patch level is shown in |
| 108 | patchlevel.h. |
| 109 | |
| 110 | |
| 111 | Just a personal note: I want you to know that I create nice things like this |
| 112 | because it pleases the Author of my story. If this bothers you, then your |
| 113 | notion of Authorship needs some revision. But you can use perl anyway. :-) |
| 114 | |
| 115 | The author. |