LAUPRETRE François (P) wrote: >> From: Greg Beaver [mailto:[EMAIL PROTECTED] > >> With all due respect, this is a rather severe exaggeration of >> PHK's talents. >> >> PHK does *not* use a standardized file format like ZIP, and >> the format is undocumented as of last Friday when I read all >> of the docs at your site. > > Right. As for phar, I didn't find a format to support every features I > wanted. You're right, it does not solve EVERY issues people raised about > phar :) The main problem, as you know, is to find a format which allows > the archive file to be included as a PHP script file. And I also wanted to > be able to set an 'interpreter' line (a line starting with '#!') at the > beginning of the file. If somebody knows a format which supports that, > please tell me.
Both phar/PHP_Archive and PHK support this. The only file format that would "allow" this kind of shebang is the tar file format, as the first element in the file is a filename. The original design of PHP_Archive used the tar file format to take advantage of this hack. > >> PHK source code is not easy to find (is it even publicly available?) > > Wrong. PHK source code is contained in the PHK_Creator package (which > inserts it in every package it creates). Either you extract it from the > PHK_Creator PHK file, or you download the PHK_Creator building kit: it is > quite the same but in tar format, with the Makefile and PSF file used to > create the creator package. I mean a public RCS like a CVS or SVN server. I found the PHK_Creator package and looked at it in order to review the source code. >> PHP_Archive (the equivalent to PHK) is only needed to create >> the .phar archives, just as PHK is needed to create PHK >> archives (no difference - external tool needed) but in both >> cases nothing is needed to run the resulting archives. > > I don't understand. In order to be able to include a phar archive, the > phar stream wrapper must have been defined previously, either by > PHP_Archive or by the PHAR extension. When you include a PHK archive, you > just need PHP version 5.1 or more, as the runtime code is included in the > archive. And, when the accelerator will be available, it will be the same > : the embedded runtime code will detect the optional accelerator and use > it transparently. This is exactly how phar/PHP_Archive works. For example: http://pear.php.net/go-pear.phar contains the complete PHP_Archive class, which will fall back to the phar extension if available. >> PHK is developed by one developer without the benefit of >> community oversight, or any evidence of interest in >> community-based open source development at all. > > This is unfair. I tried to get interest from PHP core developers from the > beginning, 18 months ago. The only replies I got were rude ones, 'what's > wrong with phar ?' style. I am probably unclear with my argument here. After a deep review of the source code, it seems to me that PHK is basically PHP_Archive with a different file format plus a few built in extras and a separate website. In other words, at the time you started the PHK project, PHP_Archive was fully functioning (version 0.6.0, released on 2005-08-30) and was backed by the officiality of being served from PEAR, a php.net site. Rather than attempt to inject your interesting ideas for the future of PHP_Archive, you seem to have actively avoided PHP_Archive and re-invented the wheel. > I don't take this as an argument, but PHAR has been developed by 3 > developers, now 2 active, with very little community interest and > oversight... On the contrary, several developers have been active in testing the extension and in reporting bugs/design flaws from the beginning. Most of the activity has been informally through IRC or through email, so this is understandably not as visible to you as it would otherwise have been. > And, if they don't, unfortunately, it will be one more reason not to > switch to PHP 6 :) I hate to be the one to burst our bubble, but unicode is a killer feature and PHP 6 will be adopted en masse, so if this isn't changed, it will simply mean the death of userspace stream wrappers for anything but custom projects. Greg -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
