#25216 [Asn->Csd]: PEAR package depends on XML_RPC but doesn't list it in package.xml
| From: | cellog@php.net | Date: | Mon, 25 Aug 2003 16:49:45 +0000 |
| Subject: | #25216 [Asn->Csd]: PEAR package depends on XML_RPC but doesn't list it in package.xml | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-20495@lists.php.net to get a copy of this message | ||
ID: 25216
Updated by: cellog@php.net
Reported By: marshall at exclupen dot com
-Status: Assigned
+Status: Closed
Bug Type: PEAR related
PHP Version: Irrelevant
Assigned To: cellog
New Comment:
This bug has been fixed in CVS.
In case this was a PHP problem, snapshots of the sources are packaged
every three hours; this change will be in the next snapshot. You can
grab the snapshot at http://snaps.php.net/.
In case this was a documentation problem, the fix will show up soon at
http://www.php.net/manual/.
In case this was a PHP.net website problem, the change will show
up on the PHP.net site and on the mirror sites in short time.
Thank you for the report, and for helping us make PHP better.
Previous Comments:
------------------------------------------------------------------------
[2003-08-24 14:13:42] cellog@php.net
That's a good idea - if you can convince the maintainer of XML_RPC to
do this, then it makes fixing pear-Package.xml easier :). However,
that's not in the scope of this bug, so you do what you can, and I'll
react.
Greg
------------------------------------------------------------------------
[2003-08-24 12:42:25] marshall at exclupen dot com
Sorry if this shows up several times... it didn't show up when I added
a comment, so now i'm using "Edit Submission".
--
Is the xmlrpc extension even needed? It seems like it could make
installation more confusing, since PEAR packages are really easy to
install, and extensions are not, especially if you're on shared
hosting. The class would be a lot simpler without it (the entire
class_epi() function could be removed), but perhaps slower. Perhaps we
could plan to add xmlrpc extension stuff to the XML_RPC package, so
you'd be guaranteed to have XML-RPC just by installing XML_RPC.
------------------------------------------------------------------------
[2003-08-24 12:14:01] cellog@php.net
Hi,
I think the best solution is to add 2 dependencies to pear-Package.xml,
after some thought. One optional dependency on the xml-rpc extension,
and one required dependency on XML_RPC, as this is the fallback by
default.
If there were a way to tell the installer "either this or the other is
needed" that would be a better solution, but there isn't :)
Greg
------------------------------------------------------------------------
[2003-08-22 20:17:27] marshall at exclupen dot com
I forgot to mention that XML_RPC should be an optional dependency,
since Remote.php will work without XML_RPC provided that the PHP
extension is installed.
------------------------------------------------------------------------
[2003-08-22 20:14:05] marshall at exclupen dot com
Description:
------------
XML_RPC is used in PEAR/Remote.php, but it isn't listed as a dependency
for the PEAR package. If XML_RPC and the xmlrpc PHP extension aren't
present, it raises an error saying that the remote features are
unavailable until XML_RPC is installed.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=25216&edit=1