Re: Re: Correct PEAR package.xml php-gtk dependencytag?

Steph, > At most, all we really need from the PEAR installer is the ability to update > an existing PHP-GTK installation and extensions as necessary. So basically > (I think) we'd only be looking at throwing an error message if someone > attempted to use the PEAR installer to install a GTK-related class when > PHP-GTK isn't loaded. That's right. > On the other hand, we need those PEAR classes to be > able to 'relate' to a loaded PHP-GTK module and extensions, and it seems the > way PEAR does this is via the package.xml system alone - am I wrong? Now I understand what you mean with "our own package.xml". You are partly right: The package.xml file contains data about the package including version information. But it's mainly used when installing the given package. Now it's just the question if we can "inject" a bogus php-gtk package in a PEAR installation when php-gtk gets installed by its own system. I doubt it, mainly because you can have many pear installations around (I'm one of these crazy people). Best thing would IMO be if there would be a special treatment for php-gtk OR even better for any extension - if it's loaded, and if it's loaded, check the version with the reflection classes as Andrei has shown us. -- Regards/MfG, Christian Weiske