text
stringlengths 0
834k
|
|---|
=item B<ppm help> [ I<subcommand> ]
|
Prints the documentation for ppm (this file).
|
=item B<ppm info> [ I<name> ]
|
List information about ppm and its environment. With argument print the
|
value of the given variable. See also L<ppm config list>.
|
=item B<ppm install> I<pkg> ... [ B<--area> I<area> ] [ B<--force> ] [ B<--nodeps> ]
|
=item B<ppm install> I<module> ... [ B<--area> I<area> ] [ B<--force> ] [ B<--nodeps> ]
|
=item B<ppm install> I<file>.ppmx [ B<--area> I<area> ] [ B<--nodeps> ]
|
=item B<ppm install> I<file>.ppd [ B<--area> I<area> ] [ B<--nodeps> ]
|
=item B<ppm install> I<url> [ B<--area> I<area> ] [ B<--nodeps> ]
|
=item B<ppm install> I<num> [ B<--area> I<area> ] [ B<--nodeps> ]
|
Install a package and its dependencies.
|
The argument to B<ppm install> can be the name of a package, the name of
|
a module provided by the package, the file name or the URL of a PPMX or PPD file,
|
or the associated number for the package returned by the last C<ppm
|
search> command.
|
Package or module names can be repeated to install multiple modules in one go.
|
These forms can also be intermixed.
|
If the package or module requested is already installed, PPM installs
|
nothing. The B<--force> option can be used to make PPM install a
|
package even if it's already present. With B<--force> PPM resolves
|
file conflicts during package installation or upgrade by allowing
|
files already installed by other packages to be overwritten and
|
ownership transferred to the new package. This may break the package
|
that originally owned the file.
|
By default, new packages are installed in the C<site> area, but if the
|
C<site> area is read only, and there are user-defined areas set up, the
|
first user-defined area is used as the default instead. Use the
|
B<--area> option to install the package into an alternative location.
|
The B<--nodeps> option makes PPM attempt to install the package
|
without resolving any dependencies the package might have.
|
=item B<ppm list> [ I<area> ] [ B<--matching> I<pattern> ] [ B<--csv> [ I<sep> ] ] [ B<--no-header> ] [ ---fields B<fieldlist> ]
|
List installed packages. If the I<area> argument is not provided, list
|
the content of all install areas.
|
The B<--matching> option limits the output to only include packages
|
matching the given I<pattern>. See B<ppm search> for I<pattern> syntax.
|
The B<--csv> option selects CSV (comma-separated values) format for the
|
output. The default field separator can be overridden by the argument
|
following B<--csv>.
|
The B<--no-header> option suppress printing of the column headings.
|
The B<--fields> argument can be used to select what fields to show.
|
The argument is a comma separated list of the following field names:
|
=over
|
=item B<name>
|
The package name. This field is always shown, but if specified
|
alone get rid of the decorative box.
|
=item B<version>
|
The version number of the package.
|
=item B<release_date>
|
The release date of the package.
|
=item B<abstract>
|
A one sentence description of the purpose of the package.
|
=item B<author>
|
The package author or maintainer.
|
=item B<area>
|
Where the package is installed.
|
=item B<files>
|
The number of files installed for the package.
|
=item B<size>
|
The combined disk space used for the package.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.