Re: Pyrus vs searching for package files
| From: | Greg Beaver | Date: | Mon, 06 Sep 2010 05:03:54 +0000 |
| Subject: | Re: Pyrus vs searching for package files | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-53767@lists.php.net to get a copy of this message | ||
On 8/22/10 7:44 PM, Daniel O'Connor wrote:
> clockwerx@sg1:~/packages-all/PHP_Shell$ php ~/pyrus.phar help package
>
> "If the package.xml is not specified, here is the search order
>
> - ./package.xml
> - if package.xml is version 1.0, ./package2.xml"
>
> clockwerx@sg1:~/packages-all/PHP_Shell$ ls
> examples *package2.xml* PHP README scripts tests
>
> clockwerx@sg1:~/packages-all/PHP_Shell$ php ~/pyrus.phar package
> Pyrus version 2.0.0a1 SHA-1: E8D2B52B1C5FB9C1F02D753BECEAB96176348F77
> Using PEAR installation found at /home/clockwerx/pear2
> PHP Notice: Undefined variable: package in
> /home/clockwerx/.pear/php/PEAR2/Pyrus/Developer/PackageFile/Commands.php on
> line 161
>
> Notice: Undefined variable: package in
> /home/clockwerx/.pear/php/PEAR2/Pyrus/Developer/PackageFile/Commands.php on
> line 161
> PHP Fatal error: Call to a member function isNewPackage() on a non-object
> in /home/clockwerx/.pear/php/PEAR2/Pyrus/Developer/PackageFile/Commands.php
> on line 161
>
> Fatal error: Call to a member function isNewPackage() on a non-object in
> /home/clockwerx/.pear/php/PEAR2/Pyrus/Developer/PackageFile/Commands.php on
> line 161
>
> # but; if we shift the package.xml, different behaviour emerges:
> clockwerx@sg1:~/packages-all/PHP_Shell$ mv package2.xml package.xml
> clockwerx@sg1:~/packages-all/PHP_Shell$ php ~/pyrus.phar package
> Pyrus version 2.0.0a1 SHA-1: E8D2B52B1C5FB9C1F02D753BECEAB96176348F77
> Using PEAR installation found at /home/clockwerx/pear2
> PEAR2\Pyrus\PackageFile\Exception: Invalid package.xml
> PEAR2\Pyrus\XMLParser\Exception: Invalid XML document
Hi Daniel,
I'm sure you worked this out ages ago, but that error is a libxml error
which only occurs when you have invalid xml like:
<?xml version="1.0" ?>
<package<>
</package>
The errors are another matter entirely.
Greg