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

Hi Scott, > > If it became a PECL package I'd have to rewrite the entire win32 build > > system from scratch :-\ > > > > Perhaps a better idea would be to figure some way to integrate > > <channel>gtk.php.net</channel> - could anyone point me to the PEAR installer > > mechanism's internals (backend) so I can look into that possibility? > > Setting up the PEAR Channel server is the easy part. I have a PEAR > server already set up that you can use to test this if you want. Just > let me know and I will create you an account. I think I just got lost somewhere down the line - my question wasn't about setting up a PEAR channel server, it was about having gtk.php.net as a channel that could be searched. Or did I grab completely the wrong end of the stick? It'd be nice to see some backend code so I could get a grip on the way the installer works... > Even if we have a PHP-GTK channel server, the PEAR/PECL installer will > still need to be used so that will still require rewriting the build system. Whoa, wait just a minute. Remember we're talking about a situation whereby PHP-GTK is never going to be enabled in a version of PHP used for the web, and PHP-GTK *always* has to be loaded via php.ini these days. So what we really need to look into is a way of checking whether the PHP-GTK module is loaded. If it isn't loaded, ipso facto we've got the wrong PHP for any GTK-related PEAR classes. That's the simple part, you'd think. > Is this a show stopper? Yes, I think it probably would be a show stopper if we had to rewrite that - not only from my perspective, but also from Andrei's, given that he's had so many struggles with the *nix setup already. > I know you just spent a lot of time > getting it to work right but I am picturing the day when someone writes > to the dev list for installation advice and we can just write back: > > $> pecl install gtk/PHP_GTK2 I think that would be problematic, for the reason given above. We don't WANT people to be able to install php-gtk in a web server environment! and the only way I can see to even halfway prevent it would be to check that the PHP used was a cli SAPI before proceeding with a PHP-GTK install... It'd be better to have our own equivalent installer on gtk.php.net IMHO, if only to avoid potential confusion. 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. 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? - Steph