Datasets:
breadlicker45
/
batch-stack-code

Dataset card Data Studio Files
xet
Community
text
stringlengths
0
834k
[ ] An inactive repository
ppm> rep up EZE
Repositories:
[1] EZE
[2] ActiveCD
[3] ActiveState Package Repository
[ ] An inactive repository
To disable the ActiveCD repository temporarily, enter the following:
ppm> rep off ActiveCD
Repositories:
[1] EZE
[2] ActiveState Package Repository
[ ] ActiveCD
[ ] An inactive repository
To describe a repository, refer to it either by name, or by the number
displayed next to the repository in the Active Repositories list. You
must refer to inactive repositories by their full name.
ppm> rep describe 2
Describing Active Repository 2:
Name: ActiveState Package Repository
Location: http://ppm.ActiveState.com/cgibin/PPM/...
Type: PPMServer 2.00
ppm> rep describe ActiveCD
Describing Inactive Repository:
Name: ActiveCD
Location: F:\PPMPackages\5.8plus
Type: Local Directory
To re-activate the ActiveCD repository, use the *rep on* command. You
must refer to inactive repositories by name, not number.
ppm> rep on ActiveCD
Active Repositories:
[1] EZE
[2] ActiveState Package Repository
[3] ActiveCD
[ ] An inactive repository
Repository Types
PPM3 supports several types of package repositories:
1. PPM Server 3
ActiveState's SOAP-driven package server. Because all searches are
done server-side, the server can deliver much richer information
about packages than other repositories.
2. PPM Server 2
The SOAP server designed for PPM version 2. PPM 3.1 ships with the
PPM2 repository as well as the PPM3 repository, so you can use
either. Simple searches are performed server-side. If your search is
too complicated for the server, PPM 3.1 will download the package
summary and search by itself.
3. Web Repositories
Older versions of PPM used non-SOAP repositories (directories full
of PPD files accessible using a web browser). Over the history of
PPM, there have been several different ways of organising the files
so that PPM can search for packages properly. PPM3 tries to download
a summary file first -- if that fails, it gets the directory index.
It parses the summary or the index, and caches it. Searches are done
from the cache.
4. FTP Repositories
FTP is another way of exposing a directory full of PPD files. PPM3
consideres FTP repositories a subset of Web repositories. Treat them
as identical: PPM3 downloads the summary or the ""index"" (file
listing in this case), parses it, and then searches from it.
5. Local Repositories
To support installing packages from the ActiveCD, a local directory
can be a repository. PPM searches the files in the directory. All
valid path formats are supported, including UNC paths.
END
sub comp_repository {
my $o = shift;
my ($word, $line, $start) = @_;
my @words = $o->line_parsed($line);
my $words = scalar @words;
my @reps = PPM::UI::repository_list()->result_l;
my $reps = @reps;
my @compls = qw(add delete describe rename set select);
push @compls, ($reps ? (1 .. $reps) : ());
if ($words == 1 or $words == 2 and $start != length($line)) {
return $o->completions($word, \@compls);
}
if ($words == 2 or $words == 3 and $start != length($line)) {
return (readline::rl_filename_list($word))
if $words[1] eq 'add';
return $o->completions($word, [1 .. $reps])
if $o->completions($words[1], [qw(delete describe rename set select)]) == 1;