So... With repsect to ISPs and conservative sysadmins not installing all kinds of good stuff from PECL...
Has anybody considered hacking ./configure in such a way that it invokes PECL install for any "extra" --enable-xxx flags that match up with stable PECL extensions? The point being that to the busy sysAdmin, it just looks like a "built-in" feature of PHP so they actually install the dang things, but all the benefits of PECL-ness are still there when it's time to upgrade that one extension. This may be a particularly stupid idea or simply not able to be done, for all I know, but it seems an interesting suggestion to this naive reader. And seems like the kind of thing that one of you gurus could hack up in about 10 minutes of shell scripting tacked onto the end of that stuff in 'configure' script. Okay, so it would then take you 10 days to debug it and make sure it works on all platforms, but still. :-) It might also forestall some of the "I want my extension in core" | "Your extension doesn't belong in core" threads here, since marking a PECL as "stable" pretty much *IS* making it available to "core" Which would then shift focus to arguments^H^H^H^H^H^H^H^H^H discussions about what gets marked "stable" in PECL, but that's probably a bit less subjective, hopefully. One could even imagine a utopia where a requirement of 95% code coverage by a suite of .phpt tests would be one objective measure for pre-qualifying a PECL extension as "stable" :-) Just an idea I thought I'd toss out [t]here. Let the flames begin. -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So? -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
