text stringlengths 0 834k |
|---|
To install a package: |
install <package_name> |
Most commands can be truncated; as long as the command is unambiguous, |
PPM will recognize it. For example, 'repository add foo' can be entered |
as 'rep add foo'. |
PPM features user profiles, which store information about installed |
packages. Profiles are stored as part of your ASPN account; thus, you |
can easily maintain package profiles for different languages, or |
configure one machine with your favorite packages, and then copy that |
installation to another machine by accessing your ASPN profile. |
For more information, type 'help profile' at the PPM prompt. |
END |
sub smry_ppm_migration { ""guide for those familiar with PPM"" } |
sub help_ppm_migration { <<'END' } |
ppm migration -- PPM Migration Guide |
Description |
Those familiar with PPM version 2 should appreciate the extended |
functionality of PPM version 3, including the command-line history, |
autocomplete and profiles. Some PPM version 2 commands are different in |
PPM version 3. Examples of command changes include: |
1 Adding a repository |
PPM2: |
set repository my_repository http://my/repository |
PPM3: |
repository add my_repository http://my/repository |
2 Removing a repository |
PPM2: |
set repository --remove my_repository |
PPM3: |
repository del my_repository |
3 Setting the temporary directory |
PPM2: |
set build DIRECTORY |
PPM3 |
set tempdir DIRECTORY |
4 Setting frequency of download updates |
PPM2: |
set downloadstatus NUMBER |
PPM3: |
set download-chunksize NUMBER |
5 Changing the installation root directory: |
PPM2: |
set root DIRECTORY |
PPM3: |
target set root DIRECTORY |
6 Listing all installed packages: |
PPM2: |
query |
PPM3: |
query * |
7 Listing all packages on server: |
PPM2: |
search |
PPM3: |
search * |
8 Enabling HTML documentation generation: |
PPM2: |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.