Change 4312
Adding a number of example scripts that show
how to get to Perforce data for a variety of
scripting languages and variety of simple tasks.
Note that Perl/Python/Ruby (and variants) are
included, but shell/batch/DCL/applescript are
not. (Am trying to stick with somewhat-portable
approaches, to make comparisons easier.)
Each program is written in the following languages/configurations:
1. Perl, calling "p4 -Ztag" for data
2. Perl, calling Tony Smith's "P4Perl" module
3. Python, calling "p4 -G" for data
4. Ruby, calling "p4 -R" for data
5. Ruby, calling Tony Smith's "P4Ruby" module
The programs do the following:
a. compare client specs to users (find old clients)
b. compare two labels
c. determine which client specs use compression.
d. determine which files need to be "p4 add'ed."
e. output list of 'opened' files, using local pathnames.
how to get to Perforce data for a variety of
scripting languages and variety of simple tasks.
Note that Perl/Python/Ruby (and variants) are
included, but shell/batch/DCL/applescript are
not. (Am trying to stick with somewhat-portable
approaches, to make comparisons easier.)
Each program is written in the following languages/configurations:
1. Perl, calling "p4 -Ztag" for data
2. Perl, calling Tony Smith's "P4Perl" module
3. Python, calling "p4 -G" for data
4. Ruby, calling "p4 -R" for data
5. Ruby, calling Tony Smith's "P4Ruby" module
The programs do the following:
a. compare client specs to users (find old clients)
b. compare two labels
c. determine which client specs use compression.
d. determine which files need to be "p4 add'ed."
e. output list of 'opened' files, using local pathnames.
Tip: Use n and p to cycle through the changes.