Links to know aboutMusic The Chiara String Quartet Chiara Quartet (MySpace) Greenwood Music Camp UNL School of Music PHP PEAR Installer Manifesto phpDocumentor PEAR phar docblock PHP_Parser PHP_Parser_DocblockParser PHP_ParserGenerator PHP_LexerGenerator PEAR_PackageFileManager PHP_Archive Games_Chess Blogs Joshua Eichorn Paul M. Jones Davey Shafik Popular EntriesSetting up your own PEAR channel with Chiara_PEAR_Server - the official way
(26) Do you develop a website? It is infinitely better to synchronize live and development sites using the PEAR Installer(24) Using PEAR 1.4.0 to install PEAR packages on a remote host(19) doing the PEAR thing(19) PEAR now fits in a bottle: meet go-pear.phar(17) CategoriesPowered by |
Wednesday, March 26. 2008behold pecl/phar and mighty PHP 5.3, also php|arch and php|tekTrackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
>Phar fully solves the problems with
>current directory and code loading/file >loading that plague all other stream >wrappers like PHP_Archive and PHK. Could you give an example of such a problem?
Sure. Many applications assume that they can load both code and configuration files using ".". For instance, phpMyAdmin loads config.inc.php via a simple include with ./config.inc.php. These calls used to go to the current directory of the phar archive on disk when inside a phar. With Phar::interceptFileFuncs() phar first checks to see if the file is inside the virtual current directory of the executing file before checking the real current directory, allowing these applications to be run unmodified from within a phar archive.
Sure. Many applications load code using things like:
require "config.php" assuming that include_path has "." as its first entry. In addition, some of the most popular apps (phpMyAdmin, for instance) explicitly use: require "./config.php" This code fails inside of a phar unless you can intercept the call to require. Even more insidious is: $a = file_get_contents('config.xml') which assumes config.xml is in the current directory - this fails without interception of these functions. pecl/phar solves all of these problems allowing code to be used unmodified inside of a phar archive
Hi Greg,
I've fixed the PEAR conflict/overlap in the schedule. Sorry about that. Too much juggling on my part. (-: S
Tsk, Greg, how can it be 'unimaginable' if we imagined it?
(My editor's hat is obviously on!) More seriously, I've been truly impressed by the time, thought and sheer effort you've put into making the extension work 'properly' rather than simply settling for 'PHP_Archive in C'. Phar's nothing like it was; it's a gen-u-ine solution now. I just hope you'll be around for long enough between gigs to get pyrus/pecl installation working this well too, so everyone can use it and the problem(s) of the PHP/PECL relationship can finally be resolved. Let's try for a full Phar 2.0 release before php|tec |
Links in this articlePEAR Installer ManifestoCalendar
QuicksearchMy Latest ReleasesTop Exitspear.php.net (387)
www.php.net (125) pecl.php.net (111) pear.chiaraquartet.net (81) php.net (46) Blog Administration |
|||||||||||||||||||||||||||||||||||||||||||||||||