Re: Phar as part of the include_path?

From: Date: Sun, 17 Feb 2008 22:24:14 +0000
Subject: Re: Phar as part of the include_path?
References: 1 2 3 4  Groups: php.pecl.dev 
Request: Send a blank email to pecl-dev+get-5121@lists.php.net to get a copy of this message
Hi Markus,
I'm specifically interesting in whether an phar can be added directly to the include_path. The examples you gave aren't an option when it comes to componized libraries like Zend or eZ. I'ld love to see support for something like include_path=/libs/zend-1.0.3.phar:/libs/ez-6.4.phar.
<sigh /> I _knew_ I'd seen something about this: <quote> cellog Wed Feb 13 15:00:30 2008 UTC Modified files: /pecl/phar func_interceptors.c phar.c phar_internal.h phar_object.c
             stream.c tar.c util.c
/pecl/phar/tests frontcontroller22.phpt Log: remove refcount hack to workaround zlib memleak fixed in zlib intercepted file functions now fall through if the file is not found in the phar, this allows access to external libraries actually use include_path for locating files for inclusion and in file_get_contents/fopen when include_path is requested. This allows applications like Zend Framework MVC implementation to function properly </quote> - I haven't updated from CVS since that commit because I've been up to the eyeballs in other things here. Perhaps you'd like to test it too and give Greg your feedback? - Steph
thanks, - Markus


« previous php.pecl.dev (#5121) next »