Lines Matching refs:bundle

68 	     autobundle bundle expand force get cvs_import
1784 my(@bundle) = $self->_u_r_common("a",@_);
1815 join("\n", @bundle),
1823 $CPAN::Frontend->myprint("\nWrote bundle file
3285 my($bundle,$id,$userid);
3309 $bundle = $1;
3312 if ($bundle){
4904 # to recurse into its prereq_pms, a bundle needs to recurse into its modules
4943 $CPAN::Frontend->mydie("I don't know a bundle with ID $id\n") unless
4987 The bundle file "$inst_file" may be a broken
4988 bundlefile. It seems not to contain any bundle definition.
5079 Carp::croak "Can't $meth $id, don't have an associated bundle file. :-(\n"
5106 $fail{$s} = 1; # the bundle itself may have succeeded but
5126 The following items in bundle %s had installation problems:},
5144 during recursive bundle calls: " unless $report_propagated++;
5157 # If a bundle contains another that contains an xs_file we have
5198 No File found for bundle } . $self->id . qq{\n}), return;
6179 C<autobundle> writes a bundle file into the
6182 installed within @INC. The name of the bundle file is based on the
6366 Returns a one-line description of the bundle
6370 Returns a multi-line description of the bundle
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
6406 Returns 1 if the bundle itself and all its members are uptodate.
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
6648 A bundle is just a perl module in the namespace Bundle:: that does not
6667 The distribution of a bundle should follow the same convention as
6671 Bundle::Tkkit' (assuming such a bundle exists), CPAN will install all
6676 modules in a snapshot bundle file.
6880 easy if you maintain a private bundle definition file. To get a useful
6881 blueprint of a bundle definition file, the command autobundle can be used
6882 on the CPAN shell command line. This command writes a bundle definition
6886 Bundle/my_bundle.pm. With a clever bundle file you can then simply say
6892 Maintaining a bundle definition file means keeping track of two
6895 attributes correctly, so a bundle definition file should specify
6898 what I try to accomplish in my private bundle file is to have the
7030 resulting bundle file (e.g. Bundle/mybundle.pm), install the new perl
7035 Install the bundle file you produced in the first step with something like