| 1 |
dist 4.0 |
| 2 |
|
| 3 |
Copyright (c) 1988, Larry Wall |
| 4 |
Copyright (c) 1990-1992, Harlan Stenn |
| 5 |
Copyright (c) 1991-1997, Raphael Manfredi |
| 6 |
Copyright (c) 2004-2006, Raphael Manfredi |
| 7 |
Copyright (c) 2007+ Many other contributors |
| 8 |
|
| 9 |
------------------------------------------------------------------------ |
| 10 |
This program is free software; you can redistribute it and/or modify |
| 11 |
it under the terms of the Artistic License, a copy of which can be |
| 12 |
found with this package. |
| 13 |
|
| 14 |
This program is distributed in the hope that it will be useful, |
| 15 |
but WITHOUT ANY WARRANTY; without even the implied warranty of |
| 16 |
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
| 17 |
Artistic License for more details. |
| 18 |
------------------------------------------------------------------------ |
| 19 |
|
| 20 |
This version of dist requires you to have at least perl 4.0 PL36. |
| 21 |
It has also been ported to work with modern perl 5. |
| 22 |
|
| 23 |
After you have unpacked your kit, you should have all the files listed |
| 24 |
in MANIFEST. |
| 25 |
|
| 26 |
======================================================================== |
| 27 |
It's not the way I wrote it, but the |
| 28 |
way you play it makes it sound a lot better. |
| 29 |
-- Camille Saint-Saens (French composer) |
| 30 |
|
| 31 |
The dist package consists of four parts: |
| 32 |
|
| 33 |
1) The Configure generator (metaconfig) and its supporting files. |
| 34 |
2) The distribution kit maker (makedist) and its supporting files. |
| 35 |
3) The patch distribution system (pat*) and its supporting files. |
| 36 |
4) The Makefile generator (jmake) and its supporting files. |
| 37 |
|
| 38 |
Each of these can be used separately from the others. Before you can |
| 39 |
use any of those, however, the directory containing your package (not this |
| 40 |
package) must be initialized by putting a .package file into it. This |
| 41 |
can be done by running packinit in that directory. |
| 42 |
|
| 43 |
Notes: |
| 44 |
|
| 45 |
If you are running on a system with <= 14 char filenames, don't |
| 46 |
distribute any files with filenames longer than 12 chars (with the |
| 47 |
exception of patchlevel.h), so that there will be room for a |
| 48 |
2-digit extension indicating patch number in your bugs direcory. |
| 49 |
This includes .SH files, so any shell script built by a .SH file |
| 50 |
should be 9 characters or less. On systems with flexfilenames you |
| 51 |
don't have to worry about it. |
| 52 |
|
| 53 |
This package has been designed on top of dist 2.0, which has been |
| 54 |
written by Larry Wall <[email protected]>. |
| 55 |
======================================================================== |
| 56 |
|
| 57 |
INSTALLATION |
| 58 |
|
| 59 |
1) Run Configure. This will figure out various things about your |
| 60 |
system. After it has completed, it will produce config.h and config.sh. |
| 61 |
|
| 62 |
You might possibly have to trim # comments from the front of Configure |
| 63 |
if your shell doesn't handle them, but all other comments will be taken |
| 64 |
care of. |
| 65 |
|
| 66 |
2) Run make. |
| 67 |
|
| 68 |
3) If make succeeded, you may wish to do "make install install.man". Be |
| 69 |
sure your rights are correct (if you install manual pages, you may need |
| 70 |
super-user privileges). By not running "make install.man", you avoid the |
| 71 |
installation of the manual pages. |
| 72 |
|
| 73 |
4) Read the manual entry before running. |
| 74 |
|
| 75 |
5) IMPORTANT! Communicate any problem and suggested patches to me, |
| 76 |
[email protected] (Raphael Manfredi), so we can keep this |
| 77 |
distribution in sync. If you have a problem, there will be someone else |
| 78 |
who had it or will have it too... |
| 79 |
|
| 80 |
If possible, send me patches such that the patch program will apply |
| 81 |
them. Context diffs are the best, then normal diffs. Do not send ed |
| 82 |
scripts, I have probably changed my copy since the version you got. |
| 83 |
|
| 84 |
6) After everything is installed, you can do make clobber. This will |
| 85 |
clean up everything and let you re-distribute this kit, without |
| 86 |
carrying useless files. You should keep this distribution intact, so |
| 87 |
that future patches will be applyable. |
| 88 |
|
| 89 |
7) If you wish to deinstall the package, you may run "make deinstall". |
| 90 |
A separate "make deinstall.man" will remove the manual pages. Be sure |
| 91 |
the makefiles are correctly set before running any deinstall target. |
| 92 |
On USG systems, some executable have a chance to remain despite the |
| 93 |
deinstall (text file busy...). |
| 94 |
|
| 95 |
Raphael Manfredi <[email protected]> |