cpan.3

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

.Vb 1
\&    cpan> notest install Tk
.Ve
.Sp
A \f(CW\*(C`clean\*(C'\fR command results in a
.Sp
.Vb 1
\&  make clean
.Ve
.Sp
being executed within the distribution file's working directory.
.ie n .IP """readme""\fR, \f(CW""perldoc""\fR, \f(CW""look"" module or distribution" 2
.el .IP "\f(CWreadme\fR, \f(CWperldoc\fR, \f(CWlook\fR module or distribution" 2
.IX Item "readme, perldoc, look module or distribution"
\&\f(CW\*(C`readme\*(C'\fR displays the \s-1README\s0 file of the associated distribution.
\&\f(CW\*(C`Look\*(C'\fR gets and untars (if not yet done) the distribution file,
changes to the appropriate directory and opens a subshell process in
that directory. \f(CW\*(C`perldoc\*(C'\fR displays the pod documentation of the
module in html or plain text format.
.ie n .IP """ls"" author" 2
.el .IP "\f(CWls\fR author" 2
.IX Item "ls author"
.PD 0
.ie n .IP """ls"" globbing_expression" 2
.el .IP "\f(CWls\fR globbing_expression" 2
.IX Item "ls globbing_expression"
.PD
The first form lists all distribution files in and below an author's
\&\s-1CPAN\s0 directory as they are stored in the \s-1CHECKUMS\s0 files distributed on
\&\s-1CPAN\s0. The listing goes recursive into all subdirectories.
.Sp
The second form allows to limit or expand the output with shell
globbing as in the following examples:
.Sp
.Vb 3
\&      ls JV/make*
\&      ls GSAR/*make*
\&      ls */*make*
.Ve
.Sp
The last example is very slow and outputs extra progress indicators
that break the alignment of the result.
.Sp
Note that globbing only lists directories explicitly asked for, for
example FOO/* will not list FOO/bar/Acme\-Sthg\-n.nn.tar.gz. This may be
regarded as a bug and may be changed in future versions.
.ie n .IP """failed""" 2
.el .IP "\f(CWfailed\fR" 2
.IX Item "failed"
The \f(CW\*(C`failed\*(C'\fR command reports all distributions that failed on one of
\&\f(CW\*(C`make\*(C'\fR, \f(CW\*(C`test\*(C'\fR or \f(CW\*(C`install\*(C'\fR for some reason in the currently
running shell session.
.IP "Persistence between sessions" 2
.IX Item "Persistence between sessions"
If the \f(CW\*(C`YAML\*(C'\fR or the \f(CW\*(C`YAML::Syck\*(C'\fR module is installed a record of
the internal state of all modules is written to disk after each step.
The files contain a signature of the currently running perl version
for later perusal.
.Sp
If the configurations variable \f(CW\*(C`build_dir_reuse\*(C'\fR is set to a true
value, then \s-1CPAN\s0.pm reads the collected \s-1YAML\s0 files. If the stored
signature matches the currently running perl the stored state is
loaded into memory such that effectively persistence between sessions
is established.
.ie n .IP "The ""force""\fR and the \f(CW""fforce"" pragma" 2
.el .IP "The \f(CWforce\fR and the \f(CWfforce\fR pragma" 2
.IX Item "The force and the fforce pragma"
To speed things up in complex installation scenarios, \s-1CPAN\s0.pm keeps
track of what it has already done and refuses to do some things a
second time. A \f(CW\*(C`get\*(C'\fR, a \f(CW\*(C`make\*(C'\fR, and an \f(CW\*(C`install\*(C'\fR are not repeated.
A \f(CW\*(C`test\*(C'\fR is only repeated if the previous test was unsuccessful. The
diagnostic message when \s-1CPAN\s0.pm refuses to do something a second time
is one of \fIHas already been \fR\f(CW\*(C`unwrapped|made|tested successfully\*(C'\fR or
something similar. Another situation where \s-1CPAN\s0 refuses to act is an
\&\f(CW\*(C`install\*(C'\fR if the according \f(CW\*(C`test\*(C'\fR was not successful.
.Sp
In all these cases, the user can override the goatish behaviour by
prepending the command with the word force, for example:
.Sp
.Vb 4
\&  cpan> force get Foo
\&  cpan> force make AUTHOR/Bar\-3.14.tar.gz
\&  cpan> force test Baz
\&  cpan> force install Acme::Meta
.Ve
.Sp
Each \fIforced\fR command is executed with the according part of its
memory erased.
.Sp
The \f(CW\*(C`fforce\*(C'\fR pragma is a variant that emulates a \f(CW\*(C`force get\*(C'\fR which
erases the entire memory followed by the action specified, effectively
restarting the whole get/make/test/install procedure from scratch.
.IP "Lockfile" 2
.IX Item "Lockfile"
Interactive sessions maintain a lockfile, per default \f(CW\*(C`~/.cpan/.lock\*(C'\fR.
Batch jobs can run without a lockfile and do not disturb each other.
.Sp
The shell offers to run in \fIdegraded mode\fR when another process is
holding the lockfile. This is an experimental feature that is not yet
tested very well. This second shell then does not write the history
file, does not use the metadata file and has a different prompt.
.IP "Signals" 2
.IX Item "Signals"
\&\s-1CPAN\s0.pm installs signal handlers for \s-1SIGINT\s0 and \s-1SIGTERM\s0. While you are
in the cpan-shell it is intended that you can press \f(CW\*(C`^C\*(C'\fR anytime and
return to the cpan-shell prompt. A \s-1SIGTERM\s0 will cause the cpan-shell
to clean up and leave the shell loop. You can emulate the effect of a
\&\s-1SIGTERM\s0 by sending two consecutive SIGINTs, which usually means by
pressing \f(CW\*(C`^C\*(C'\fR twice.
.Sp
\&\s-1CPAN\s0.pm ignores a \s-1SIGPIPE\s0. If the user sets \f(CW\*(C`inactivity_timeout\*(C'\fR, a
\&\s-1SIGALRM\s0 is used during the run of the \f(CW\*(C`perl Makefile.PL\*(C'\fR or \f(CW\*(C`perl
Build.PL\*(C'\fR subprocess.
.Sh "CPAN::Shell"
.IX Subsection "CPAN::Shell"
The commands that are available in the shell interface are methods in
the package CPAN::Shell. If you enter the shell command, all your
input is split by the \fIText::ParseWords::shellwords()\fR routine which
acts like most shells do. The first word is being interpreted as the
method to be called and the rest of the words are treated as arguments
to this method. Continuation lines are supported if a line ends with a
literal backslash.
.Sh "autobundle"
.IX Subsection "autobundle"
\&\f(CW\*(C`autobundle\*(C'\fR writes a bundle file into the
\&\f(CW\*(C`$CPAN::Config\->{cpan_home}/Bundle\*(C'\fR directory. The file contains
a list of all modules that are both available from \s-1CPAN\s0 and currently
installed within \f(CW@INC\fR. The name of the bundle file is based on the
current date and a counter.
.Sh "hosts"
.IX Subsection "hosts"
Note: this feature is still in alpha state and may change in future
versions of \s-1CPAN\s0.pm
.PP
This commands provides a statistical overview over recent download
activities. The data for this is collected in the \s-1YAML\s0 file
\&\f(CW\*(C`FTPstats.yml\*(C'\fR in your \f(CW\*(C`cpan_home\*(C'\fR directory. If no \s-1YAML\s0 module is
configured or \s-1YAML\s0 not installed, then no stats are provided.
.Sh "mkmyconfig"
.IX Subsection "mkmyconfig"
\&\fImkmyconfig()\fR writes your own CPAN::MyConfig file into your ~/.cpan/
directory so that you can save your own preferences instead of the
system wide ones.
.Sh "recent ***EXPERIMENTAL COMMAND***"
.IX Subsection "recent ***EXPERIMENTAL COMMAND***"
The \f(CW\*(C`recent\*(C'\fR command downloads a list of recent uploads to \s-1CPAN\s0 and
displays them \fIslowly\fR. While the command is running \f(CW$SIG\fR{\s-1INT\s0} is
defined to mean that the loop shall be left after having displayed the
current item.
.PP
\&\fBNote\fR: This command requires XML::LibXML installed.
.PP
\&\fBNote\fR: This whole command currently is a bit klunky and will
probably change in future versions of \s-1CPAN\s0.pm but the general
approach will likely stay.
.PP
\&\fBNote\fR: See also smoke
.Sh "recompile"
.IX Subsection "recompile"
\&\fIrecompile()\fR is a very special command in that it takes no argument and
runs the make/test/install cycle with brute force over all installed
dynamically loadable extensions (aka \s-1XS\s0 modules) with 'force' in
effect. The primary purpose of this command is to finish a network
installation. Imagine, you have a common source tree for two different
architectures. You decide to do a completely independent fresh
installation. You start on one architecture with the help of a Bundle
file produced earlier. \s-1CPAN\s0 installs the whole Bundle for you, but
when you try to repeat the job on the second architecture, \s-1CPAN\s0
responds with a \f(CW"Foo up to date"\fR message for all modules. So you
invoke \s-1CPAN\s0's recompile on the second architecture and you're done.
.PP
Another popular use for \f(CW\*(C`recompile\*(C'\fR is to act as a rescue in case your
perl breaks binary compatibility. If one of the modules that \s-1CPAN\s0 uses
is in turn depending on binary compatibility (so you cannot run \s-1CPAN\s0
commands), then you should try the CPAN::Nox module for recovery.
.Sh "report Bundle|Distribution|Module"
.IX Subsection "report Bundle|Distribution|Module"
The \f(CW\*(C`report\*(C'\fR command temporarily turns on the \f(CW\*(C`test_report\*(C'\fR config
variable, then runs the \f(CW\*(C`force test\*(C'\fR command with the given
arguments. The \f(CW\*(C`force\*(C'\fR pragma is used to re-run the tests and repeat
every step that might have failed before.
.Sh "smoke ***EXPERIMENTAL COMMAND***"
.IX Subsection "smoke ***EXPERIMENTAL COMMAND***"
\&\fB*** \s-1WARNING:\s0 this command downloads and executes software from \s-1CPAN\s0 to
your computer of completely unknown status. You should never do
this with your normal account and better have a dedicated well
separated and secured machine to do this. ***\fR
.PP
The \f(CW\*(C`smoke\*(C'\fR command takes the list of recent uploads to \s-1CPAN\s0 as
provided by the \f(CW\*(C`recent\*(C'\fR command and tests them all. While the
command is running \f(CW$SIG\fR{\s-1INT\s0} is defined to mean that the current item
shall be skipped.
.PP
\&\fBNote\fR: This whole command currently is a bit klunky and will
probably change in future versions of \s-1CPAN\s0.pm but the general
approach will likely stay.
.PP
\&\fBNote\fR: See also recent
.Sh "upgrade [Module|/Regex/]..."
.IX Subsection "upgrade [Module|/Regex/]..."
The \f(CW\*(C`upgrade\*(C'\fR command first runs an \f(CW\*(C`r\*(C'\fR command with the given
arguments and then installs the newest versions of all modules that
were listed by that.
.ie n .Sh "The four ""CPAN::*"" Classes: Author, Bundle, Module, Distribution"
.el .Sh "The four \f(CWCPAN::*\fP Classes: Author, Bundle, Module, Distribution"
.IX Subsection "The four CPAN::* Classes: Author, Bundle, Module, Distribution"
Although it may be considered internal, the class hierarchy does matter
for both users and programmer. \s-1CPAN\s0.pm deals with above mentioned four
classes, and all those classes share a set of methods. A classical
single polymorphism is in effect. A metaclass object registers all
objects of all kinds and indexes them with a string. The strings
referencing objects have a separated namespace (well, not completely
separated):
.PP
.Vb 1
\&         Namespace                         Class
\&
\&   words containing a "/" (slash)      Distribution
\&    words starting with Bundle::          Bundle
\&          everything else            Module or Author
.Ve
.PP
Modules know their associated Distribution objects. They always refer
to the most recent official release. Developers may mark their releases
as unstable development versions (by inserting an underbar into the
module version number which will also be reflected in the distribution
name when you run 'make dist'), so the really hottest and newest
distribution is not always the default.  If a module Foo circulates
on \s-1CPAN\s0 in both version 1.23 and 1.23_90, \s-1CPAN\s0.pm offers a convenient
way to install version 1.23 by saying
.PP
.Vb 1
\&    install Foo
.Ve
.PP
This would install the complete distribution file (say
BAR/Foo\-1.23.tar.gz) with all accompanying material. But if you would
like to install version 1.23_90, you need to know where the
distribution file resides on \s-1CPAN\s0 relative to the authors/id/
directory. If the author is \s-1BAR\s0, this might be BAR/Foo\-1.23_90.tar.gz;
so you would have to say
.PP
.Vb 1
\&    install BAR/Foo\-1.23_90.tar.gz
.Ve
.PP
The first example will be driven by an object of the class
CPAN::Module, the second by an object of class CPAN::Distribution.
.Sh "Integrating local directories"
.IX Subsection "Integrating local directories"
Note: this feature is still in alpha state and may change in future
versions of \s-1CPAN\s0.pm
.PP
Distribution objects are normally distributions from the \s-1CPAN\s0, but
there is a slightly degenerate case for Distribution objects, too, of
projects held on the local disk. These distribution objects have the
same name as the local directory and end with a dot. A dot by itself
is also allowed for the current directory at the time \s-1CPAN\s0.pm was
used. All actions such as \f(CW\*(C`make\*(C'\fR, \f(CW\*(C`test\*(C'\fR, and \f(CW\*(C`install\*(C'\fR are applied
directly to that directory. This gives the command \f(CW\*(C`cpan .\*(C'\fR an
interesting touch: while the normal mantra of installing a \s-1CPAN\s0 module
without \s-1CPAN\s0.pm is one of
.PP
.Vb 5
\&    perl Makefile.PL                 perl Build.PL
\&           ( go and get prerequisites )
\&    make                             ./Build
\&    make test                        ./Build test
\&    make install                     ./Build install
.Ve
.PP
the command \f(CW\*(C`cpan .\*(C'\fR does all of this at once. It figures out which
of the two mantras is appropriate, fetches and installs all
prerequisites, cares for them recursively and finally finishes the
installation of the module in the current directory, be it a \s-1CPAN\s0
module or not.
.PP
The typical usage case is for private modules or working copies of
projects from remote repositories on the local disk.
.SH "CONFIGURATION"
.IX Header "CONFIGURATION"
When the \s-1CPAN\s0 module is used for the first time, a configuration
dialog tries to determine a couple of site specific options. The
result of the dialog is stored in a hash reference \f(CW $CPAN::Config \fR
in a file CPAN/Config.pm.
.PP
The default values defined in the CPAN/Config.pm file can be
overridden in a user specific file: CPAN/MyConfig.pm. Such a file is
best placed in \f(CW$HOME\fR/.cpan/CPAN/MyConfig.pm, because \f(CW$HOME\fR/.cpan is
added to the search path of the \s-1CPAN\s0 module before the \fIuse()\fR or
\&\fIrequire()\fR statements. The mkmyconfig command writes this file for you.
.PP
The \f(CW\*(C`o conf\*(C'\fR command has various bells and whistles:
.IP "completion support" 4
.IX Item "completion support"