Subversion Repositories Applications.gtt

Rev

Go to most recent revision | Details | Last modification | View Log | RSS feed

Rev Author Line No. Line
94 jpm 1
<commands version="1.0">
2
 <pickle>
3
  <summary>Build PECL Package</summary>
4
  <function>doPackage</function>
5
  <shortcut>pi</shortcut>
6
  <options>
7
   <nocompress>
8
    <shortopt>Z</shortopt>
9
    <doc>Do not gzip the package file</doc>
10
   </nocompress>
11
   <showname>
12
    <shortopt>n</shortopt>
13
    <doc>Print the name of the packaged file.</doc>
14
   </showname>
15
  </options>
16
  <doc>[descfile] [descfile2]
17
Creates a PECL package from its description file (usually called
18
package.xml).  If a second packagefile is passed in, then
19
the packager will check to make sure that one is a package.xml
20
version 1.0, and the other is a package.xml version 2.0.  The
21
package.xml version 1.0 will be saved as &quot;package.xml&quot; in the archive,
22
and the other as &quot;package2.xml&quot; in the archive&quot;
23
 
24
If no second file is passed in, and [descfile] is a package.xml 2.0,
25
an automatic conversion will be made to a package.xml 1.0.  Note that
26
only simple package.xml 2.0 will be converted.  package.xml 2.0 with:
27
 
28
 - dependency types other than required/optional PECL package/ext/php/pearinstaller
29
 - more than one extsrcrelease/zendextsrcrelease
30
 - zendextbinrelease, extbinrelease, phprelease, or bundle release type
31
 - dependency groups
32
 - ignore tags in release filelist
33
 - tasks other than replace
34
 - custom roles
35
 
36
will cause pickle to fail, and output an error message.  If your package2.xml
37
uses any of these features, you are best off using PEAR_PackageFileManager to
38
generate both package.xml.</doc>
39
 </pickle>
40
</commands>