perlmodinstall.1

视频监控网络部分的协议ddns,的模块的实现代码,请大家大胆指正.

\&\fBIf you're using a Macintosh with \*(L"Classic\*(R" MacOS and MacPerl,\fR
.Sp
A. \s-1DECOMPRESS\s0
.Sp
First, make sure you have the latest \fBcpan-mac\fR distribution (
http://www.cpan.org/authors/id/CNANDOR/ ), which has utilities for
doing all of the steps.  Read the cpan-mac directions carefully and
install it.  If you choose not to use cpan-mac for some reason, there
are alternatives listed here.
.Sp
After installing cpan-mac, drop the module archive on the
\&\fBuntarzipme\fR droplet, which will decompress and unpack for you.
.Sp
\&\fBOr\fR, you can either use the shareware \fBStuffIt Expander\fR program
( http://www.aladdinsys.com/expander/ )
in combination with \fBDropStuff with Expander Enhancer\fR
( http://www.aladdinsys.com/dropstuff/ )
or the freeware \fBMacGzip\fR program (
http://persephone.cps.unizar.es/general/gente/spd/gzip/gzip.html ).
.Sp
B. \s-1UNPACK\s0
.Sp
If you're using untarzipme or StuffIt, the archive should be extracted
now.  \fBOr\fR, you can use the freeware \fBsuntar\fR or \fITar\fR (
http://hyperarchive.lcs.mit.edu/HyperArchive/Archive/cmp/ ).
.Sp
C. \s-1BUILD\s0
.Sp
Check the contents of the distribution.
Read the module's documentation, looking for
reasons why you might have trouble using it with MacPerl.  Look for
\&\fI.xs\fR and \fI.c\fR files, which normally denote that the distribution
must be compiled, and you cannot install it \*(L"out of the box.\*(R"
(See \*(L"\s-1PORTABILITY\s0\*(R".)
.Sp
If a module does not work on MacPerl but should, or needs to be
compiled, see if the module exists already as a port on the
MacPerl Module Porters site ( http://pudge.net/mmp/ ).
For more information on doing \s-1XS\s0 with MacPerl yourself, see
Arved Sandstrom's \s-1XS\s0 tutorial ( http://macperl.com/depts/Tutorials/ ),
and then consider uploading your binary to the \s-1CPAN\s0 and
registering it on the \s-1MMP\s0 site.
.Sp
D. \s-1INSTALL\s0
.Sp
If you are using cpan-mac, just drop the folder on the
\&\fBinstallme\fR droplet, and use the module.
.Sp
\&\fBOr\fR, if you aren't using cpan-mac, do some manual labor.
.Sp
Make sure the newlines for the modules are in Mac format, not Unix format.
If they are not then you might have decompressed them incorrectly.  Check
your decompression and unpacking utilities settings to make sure they are
translating text files properly.
.Sp
As a last resort, you can use the perl one-liner:
.Sp
.Vb 1
\&    perl \-i.bak \-pe \*(Aqs/(?:\e015)?\e012/\e015/g\*(Aq <filenames>
.Ve
.Sp
on the source files.
.Sp
Then move the files (probably just the \fI.pm\fR files, though there
may be some additional ones, too; check the module documentation)
to their final destination: This will
most likely be in \f(CW\*(C`$ENV{MACPERL}site_lib:\*(C'\fR (i.e.,
\&\f(CW\*(C`HD:MacPerl folder:site_lib:\*(C'\fR).  You can add new paths to
the default \f(CW@INC\fR in the Preferences menu item in the
MacPerl application (\f(CW\*(C`$ENV{MACPERL}site_lib:\*(C'\fR is added
automagically).  Create whatever directory structures are required
(i.e., for \f(CW\*(C`Some::Module\*(C'\fR, create
\&\f(CW\*(C`$ENV{MACPERL}site_lib:Some:\*(C'\fR and put
\&\f(CW\*(C`Module.pm\*(C'\fR in that directory).
.Sp
Then run the following script (or something like it):
.Sp
.Vb 4
\&     #!perl \-w
\&     use AutoSplit;
\&     my $dir = "${MACPERL}site_perl";
\&     autosplit("$dir:Some:Module.pm", "$dir:auto", 0, 1, 1);
.Ve
.IP "\(bu" 4
\&\fBIf you're on the \s-1DJGPP\s0 port of \s-1DOS\s0,\fR
.Sp
.Vb 1
\&   A. DECOMPRESS
.Ve
.Sp
djtarx ( ftp://ftp.simtel.net/pub/simtelnet/gnu/djgpp/v2/ )
will both uncompress and unpack.
.Sp
.Vb 1
\&   B. UNPACK
.Ve
.Sp
See above.
.Sp
.Vb 1
\&   C. BUILD
.Ve
.Sp
Go into the newly-created directory and type:
.Sp
.Vb 2
\&      perl Makefile.PL
\&      make test
.Ve
.Sp
You will need the packages mentioned in \fI\s-1README\s0.dos\fR
in the Perl distribution.
.Sp
.Vb 1
\&   D. INSTALL
.Ve
.Sp
While still in that directory, type:
.Sp
.Vb 1
\&     make install
.Ve
.Sp
You will need the packages mentioned in \fI\s-1README\s0.dos\fR in the Perl distribution.
.IP "\(bu" 4
\&\fBIf you're on \s-1OS/2\s0,\fR
.Sp
Get the \s-1EMX\s0 development suite and gzip/tar, from either Hobbes (
http://hobbes.nmsu.edu ) or Leo ( http://www.leo.org ), and then follow
the instructions for Unix.
.IP "\(bu" 4
\&\fBIf you're on \s-1VMS\s0,\fR
.Sp
When downloading from \s-1CPAN\s0, save your file with a \f(CW\*(C`.tgz\*(C'\fR
extension instead of \f(CW\*(C`.tar.gz\*(C'\fR.  All other periods in the
filename should be replaced with underscores.  For example,
\&\f(CW\*(C`Your\-Module\-1.33.tar.gz\*(C'\fR should be downloaded as
\&\f(CW\*(C`Your\-Module\-1_33.tgz\*(C'\fR.
.Sp
A. \s-1DECOMPRESS\s0
.Sp
Type
.Sp
.Vb 1
\&    gzip \-d Your\-Module.tgz
.Ve
.Sp
or, for zipped modules, type
.Sp
.Vb 1
\&    unzip Your\-Module.zip
.Ve
.Sp
Executables for gzip, zip, and VMStar:
.Sp
.Vb 2
\&    http://www.openvms.digital.com/freeware/
\&    http://www.crinoid.com/utils/
.Ve
.Sp
and their source code:
.Sp
.Vb 1
\&    http://www.fsf.org/order/ftp.html
.Ve
.Sp
Note that \s-1GNU\s0's gzip/gunzip is not the same as Info-ZIP's zip/unzip
package.  The former is a simple compression tool; the latter permits
creation of multi-file archives.
.Sp
B. \s-1UNPACK\s0
.Sp
If you're using VMStar:
.Sp
.Vb 1
\&     VMStar xf Your\-Module.tar
.Ve
.Sp
Or, if you're fond of \s-1VMS\s0 command syntax:
.Sp
.Vb 1
\&     tar/extract/verbose Your_Module.tar
.Ve
.Sp
C. \s-1BUILD\s0
.Sp
Make sure you have \s-1MMS\s0 (from Digital) or the freeware \s-1MMK\s0 ( available
from MadGoat at http://www.madgoat.com ).  Then type this to create
the \s-1DESCRIP\s0.MMS for the module:
.Sp
.Vb 1
\&    perl Makefile.PL
.Ve
.Sp
Now you're ready to build:
.Sp
.Vb 1
\&    mms test
.Ve
.Sp
Substitute \f(CW\*(C`mmk\*(C'\fR for \f(CW\*(C`mms\*(C'\fR above if you're using \s-1MMK\s0.
.Sp
D. \s-1INSTALL\s0
.Sp
Type
.Sp
.Vb 1
\&    mms install
.Ve
.Sp
Substitute \f(CW\*(C`mmk\*(C'\fR for \f(CW\*(C`mms\*(C'\fR above if you're using \s-1MMK\s0.
.IP "\(bu" 4
\&\fBIf you're on \s-1MVS\s0\fR,
.Sp
Introduce the \fI.tar.gz\fR file into an \s-1HFS\s0 as binary; don't translate from
\&\s-1ASCII\s0 to \s-1EBCDIC\s0.
.Sp
A. \s-1DECOMPRESS\s0
.Sp
Decompress the file with \f(CW\*(C`gzip \-d yourmodule.tar.gz\*(C'\fR
.Sp
You can get gzip from
http://www.s390.ibm.com/products/oe/bpxqp1.html
.Sp
B. \s-1UNPACK\s0
.Sp
Unpack the result with
.Sp
.Vb 1
\&     pax \-o to=IBM\-1047,from=ISO8859\-1 \-r < yourmodule.tar
.Ve
.Sp
The \s-1BUILD\s0 and \s-1INSTALL\s0 steps are identical to those for Unix.  Some
modules generate Makefiles that work better with \s-1GNU\s0 make, which is
available from http://www.mks.com/s390/gnu/
.SH "PORTABILITY"
.IX Header "PORTABILITY"
Note that not all modules will work with on all platforms.
See perlport for more information on portability issues.
Read the documentation to see if the module will work on your
system.  There are basically three categories
of modules that will not work \*(L"out of the box\*(R" with all
platforms (with some possibility of overlap):
.IP "\(bu" 4
\&\fBThose that should, but don't.\fR  These need to be fixed; consider
contacting the author and possibly writing a patch.
.IP "\(bu" 4
\&\fBThose that need to be compiled, where the target platform
doesn't have compilers readily available.\fR  (These modules contain
\&\fI.xs\fR or \fI.c\fR files, usually.)  You might be able to find
existing binaries on the \s-1CPAN\s0 or elsewhere, or you might
want to try getting compilers and building it yourself, and then
release the binary for other poor souls to use.
.IP "\(bu" 4
\&\fBThose that are targeted at a specific platform.\fR
(Such as the Win32:: modules.)  If the module is targeted
specifically at a platform other than yours, you're out
of luck, most likely.
.PP
Check the \s-1CPAN\s0 Testers if a module should work with your platform
but it doesn't behave as you'd expect, or you aren't sure whether or
not a module will work under your platform.  If the module you want
isn't listed there, you can test it yourself and let \s-1CPAN\s0 Testers know,
you can join \s-1CPAN\s0 Testers, or you can request it be tested.
.PP
.Vb 1
\&    http://testers.cpan.org/
.Ve
.SH "HEY"
.IX Header "HEY"
If you have any suggested changes for this page, let me know.  Please
don't send me mail asking for help on how to install your modules.
There are too many modules, and too few Orwants, for me to be able to
answer or even acknowledge all your questions.  Contact the module
author instead, or post to comp.lang.perl.modules, or ask someone
familiar with Perl on your operating system.
.SH "AUTHOR"
.IX Header "AUTHOR"
Jon Orwant
.PP
[e-mail]
.PP
with invaluable help from Chris Nandor, and valuable help from Brandon
Allbery, Charles Bailey, Graham Barr, Dominic Dunlop, Jarkko
Hietaniemi, Ben Holzman, Tom Horsley, Nick Ing-Simmons, Tuomas
J. Lukka, Laszlo Molnar, Alan Olsen, Peter Prymmer, Gurusamy Sarathy,
Christoph Spalinger, Dan Sugalski, Larry Virden, and Ilya Zakharevich.
.PP
First version July 22, 1998; last revised November 21, 2001.
.SH "COPYRIGHT"
.IX Header "COPYRIGHT"
Copyright (C) 1998, 2002, 2003 Jon Orwant.  All Rights Reserved.
.PP
Permission is granted to make and distribute verbatim copies of this
documentation provided the copyright notice and this permission notice are
preserved on all copies.
.PP
Permission is granted to copy and distribute modified versions of this
documentation under the conditions for verbatim copying, provided also
that they are marked clearly as modified versions, that the authors'
names and title are unchanged (though subtitles and additional
authors' names may be added), and that the entire resulting derived
work is distributed under the terms of a permission notice identical
to this one.
.PP
Permission is granted to copy and distribute translations of this
documentation into another language, under the above conditions for
modified versions.