Na}{

File Content: `Pickle.xml`

<commands version="1.0">
 <pickle>
  <summary>Build PECL Package</summary>
  <function>doPackage</function>
  <shortcut>pi</shortcut>
  <options>
   <nocompress>
    <shortopt>Z</shortopt>
    <doc>Do not gzip the package file</doc>
   </nocompress>
   <showname>
    <shortopt>n</shortopt>
    <doc>Print the name of the packaged file.</doc>
   </showname>
  </options>
  <doc>[descfile]
Creates a PECL package from its package2.xml file.

An automatic conversion will be made to a package.xml 1.0 and written out to
disk in the current directory as &quot;package.xml&quot;.  Note that
only simple package.xml 2.0 will be converted.  package.xml 2.0 with:

 - dependency types other than required/optional PECL package/ext/php/pearinstaller
 - more than one extsrcrelease or zendextsrcrelease
 - zendextbinrelease, extbinrelease, phprelease, or bundle release type
 - dependency groups
 - ignore tags in release filelist
 - tasks other than replace
 - custom roles

will cause pickle to fail, and output an error message.  If your package2.xml
uses any of these features, you are best off using PEAR_PackageFileManager to
generate both package.xml.
</doc>
 </pickle>
</commands>

Name	Size	Permission
Auth.php	2570 bytes	0644
Auth.xml	1228 bytes	0644
Build.php	2262 bytes	0644
Build.xml	260 bytes	0644
Channels.php	33444 bytes	0644
Channels.xml	4218 bytes	0644
Common.php	8221 bytes	0644
Config.php	15466 bytes	0644
Config.xml	3382 bytes	0644
Install.php	50759 bytes	0644
Install.xml	8574 bytes	0644
Mirror.php	4509 bytes	0644
Mirror.xml	617 bytes	0644
Package.php	40206 bytes	0644
Package.xml	7222 bytes	0644
Pickle.php	15894 bytes	0644
Pickle.xml	1179 bytes	0644
Registry.php	46258 bytes	0644
Registry.xml	1790 bytes	0644
Remote.php	29982 bytes	0644
Remote.xml	3311 bytes	0644
Test.php	12135 bytes	0644
Test.xml	1641 bytes	0644

File Content: Pickle.xml

File Content: `Pickle.xml`