Lines Matching refs:in
211 # use in that
223 $CPAN::Frontend->myprint("\n$redef subroutines in ".
358 # or, if it was already in the queue, I spliced and let it bypass the
364 # (1) looks at the first item in the queue without shifting it off
369 # even if the item isn't the first in the queue anymore* (that way
373 # want to retry later. That's easy if we have it twice in the queue.
376 # than two lives in the queue. Simplest example is triggered by 'install
378 # get in the way. I wanted the queue manager to be a dumb servant, not
381 # Who would I tell in this model that the user wants to be asked before
386 # in CPAN::Distribution::rematein.
455 # warn "in exists what[$what] all[@all] exists[$exists]";
489 # Called by shell, not in batch mode. In batch mode I see no risk in
603 this variable in either
635 # to whether you were in an eval or not. As a global backstop, it should
749 ### warn "$file in %INC"; #debug
753 # perfect and if we have installed the module in the meantime,
926 $CPAN::Frontend->mywarn("Warning: weird direntry in $dir: $_\n");
1145 # defaults for users, and the values can be changed in a per-user
1311 You may edit key values in the follow fashion (the "o" is a literal
1363 ls AUTHOR about files in the author's directory
1371 look open subshell in these dists' directories
1448 sub m { # emacs confused here }; sub mimimimimi { # emacs in sync here
1667 $CPAN::Frontend->myprint(sprintf "%d matches in the database\n", $expand);
1724 "in CPAN file"
1820 "by the autobundle routine in CPAN.pm.\n",
1878 "Bug in CPAN: Empty id on obj[%s][%s]",
1899 die "equal sign in command disabled (immature interface), ".
2058 # around in addition to the counter, so I'd prefer to set the
2125 $obj->$pragma($meth); # the pragma "force" in
2217 # call SUPER::mirror, we relly call the mirror method in
2227 # password has changed in the meantime, so I'm trying once again without
2312 # available in CHECKSUMS file
2369 # > Example of when I use it manually in my own stuff:
2439 qq{Please check, if the URLs I found in your configuration file \(}.
2532 # Alan Burlison informed me that in firewall environments
3015 # support came in? The RCS file is difficult to read on that:-(
3315 # in common with modules.
3317 # Changed in 1.57_63: seems like memory bloat now without
3371 CPAN->debug("deleting ID[$o->{ID}] in class[$class]")
3432 $CPAN::Frontend->mywarn($@) if $@; # ?? missing "\n" after $@ in mywarn ??
3445 $CPAN::Frontend->mywarn($@) if $@; # ?? missing "\n" after $@ in mywarn ??
3477 $CPAN::Frontend->myprint("Warning: Found no data in $metadata_file\n");
3482 "in $metadata_file\n");
3655 $CPAN::Frontend->myprint("No files in the directory of $id\n");
3660 $CPAN::Frontend->myprint("No files in the directory of $id\n");
3881 $note = "Note: Current database in memory was generated ".
3933 # we are still in the tmp directory!
3987 # renaming of a directory in some environments.
4102 Trying to open a subshell in the build directory...
4327 Warning: No md5 checksum for $basename in $chk_file.
4357 # Both modules and distributions know if "force" is in effect by
4363 # attributes. We try to correct for it currently in the read_metadata
4365 # works out in one of v1.57_53ff
4631 # check, because if 'force' is in effect, nobody else will check.
4940 # Try to get at it in the cpan directory
5038 Carp::croak("Couldn't find a Bundle file in $where");
5043 # shadowing effect. As it makes no sense to take the first in @INC for
5104 # to me in a
5126 The following items in bundle %s had installation problems:},
5460 # I believe this is always a bug in the index and should be reported
5603 # there was a bug in 5.6.0 that let lots of unini warnings out of
5627 # Seems cleaner to hold it in memory as a string starting with a "v"
5688 # After I had reread the documentation in zlib.h, I discovered that
5844 # it revealed a bug in Archive::Tar. Code is only here to hunt
5845 # the bug again. It should never be enabled in published code.
6030 (Comprehensive Perl Archive Network) sites and unpacked in a dedicated
6039 of what has been fetched, built and installed in the current
6046 that indexes all documents available in CPAN authors directories. If
6052 All other methods provided are accessible in a programmer style and in an
6100 a module, CPAN determines the distribution file in which this module
6101 is included and processes that, following any dependencies named in
6114 I<module up to date> in the case that the distribution file containing
6133 A C<clean> command results in a
6144 appropriate directory and opens a subshell process in that directory.
6148 C<ls> lists all distribution files in and below an author's CPAN
6156 in the cpan-shell it is intended that you can press C<^C> anytime and
6169 The commands that are available in the shell interface are methods in
6187 recompile() is a very special command in that it takes no argument and
6189 dynamically loadable extensions (aka XS modules) with 'force' in
6199 Another popular use for C<recompile> is to act as a rescue in case your
6201 is in turn depending on binary compatibility (so you cannot run CPAN
6209 single polymorphism is in effect. A metaclass object registers all
6223 module version number which will also be reflected in the distribution
6226 on CPAN in both version 1.23 and 1.23_90, CPAN.pm offers a convenient
6247 functions in the calling package (C<install(...)>).
6250 CPAN::Shell. All commands that are available in the CPAN shell are
6275 functionalities that are available in the shell.
6291 print "No VERSION in ", $mod->id, "\n";
6302 If you don't want to get any output in the case that all modules are
6307 If you prefer to do it more in a programmer style in one single
6334 =head2 Methods in the other Classes
6374 Recursively runs the C<clean> method on all items contained in the bundle.
6378 Returns a list of objects' IDs contained in a bundle. The associated
6392 Recursively runs the C<get> method on all items contained in the bundle
6396 Returns the highest installed version of the bundle in either @INC or
6410 Recursively runs the C<install> method on all items contained in the bundle
6414 Recursively runs the C<make> method on all items contained in the bundle
6418 Recursively runs the C<readme> method on all items contained in the bundle
6422 Recursively runs the C<test> method on all items contained in the bundle
6439 Returns a list of IDs of modules contained in a distribution file.
6440 Only works for distributions listed in the 02packages.details.txt.gz
6475 yet been run, it will be run first. A C<make test> will be issued in
6502 as the PREREQ_PM hash in the Makefile.PL. Note: works only after an
6509 through the pager specified in C<$CPAN::Config->{pager}>.
6518 Returns 1 if all the modules contained in the distribution are
6564 modules listed in The Module List (CPAN/modules/00modlist.long.html
6581 Returns the filename of the module found in @INC. The first file found
6587 Returns the version number of the module in readable format.
6634 (in MB). The contents of this cache may be used for later
6648 A bundle is just a perl module in the namespace Bundle:: that does not
6665 as in the man page header.
6670 Bundles are treated specially in the CPAN package. If you say 'install
6672 the modules in the CONTENTS section of the pod. You can install your
6674 your @INC path. The autobundle() command which is available in the
6676 modules in a snapshot bundle file.
6698 declare their $VERSION variable in an easy to parse manner. This
6725 For code debugging in interactive mode you can try "o debug" which
6727 should know that "o debug" has built-in completion support.
6748 result of the dialog is stored in a hash reference C< $CPAN::Config >
6749 in a file CPAN/Config.pm.
6751 The default values defined in the CPAN/Config.pm file can be
6752 overridden in a user specific file: CPAN/MyConfig.pm. Such a file is
6753 best placed in $HOME/.cpan/CPAN/MyConfig.pm, because $HOME/.cpan is
6758 issueing the command C< o conf init > in the CPAN shell.
6760 Currently the following keys in the hash reference $CPAN::Config are
6768 dontload_hash anonymous hash: modules in the keys will not be
6772 histsize maximum number of lines to keep in histfile
6777 keep_source_where directory in which to keep the source (if we do)
6799 You can set and query each of these options interactively in the cpan
6814 prints the current value of the I<list option> in MakeMaker's
6819 shifts or pops the array in the I<list option> variable
6864 There's no strong security layer in CPAN.pm. CPAN.pm helps you to
6873 Most functions in package CPAN are exported per default. The reason
6898 what I try to accomplish in my private bundle file is to have the
6899 packages that need to be configured early in the file and the gentle
6923 or in your web browser you have to set proxy information then you know
6946 FTP connections need to be done in a passive mode.
6961 This is the firewall implemented in the Linux kernel, it allows you to
7007 happen if a module installs itself into a different directory in the
7021 may install where in the @INC path and who uses which @INC array. In
7035 Install the bundle file you produced in the first step with something like
7051 so that STDOUT is captured in a file for later inspection.
7056 I am not root, how can I install a module in a personal directory?
7076 Another thing you should bear in mind is that the UNINST parameter
7093 install, it just uses data found in the generated Makefile. An
7097 CPAN.pm does not know the dependency tree in advance and cannot sort
7098 the queue of things to install in a topologically correct order. It
7103 situation for dependencies on CPAN in general, but this will still
7119 Some versions of readline are picky about capitalization in the
7121 /etc/inputrc that contains the word C<on> in lowercase. Change the
7126 Some authors have strange characters in their names.
7130 term_is_latin to a true value in your config file. One way of doing so