(Also CC-ig King Of PECL :)
while hunting down some information about some PECL/PEAR related things, i found it very disturbing to have "no version, might be cvs only" as the Version-Information for the functions created by those extensions.
We should change that to be of something more meaning full, maybe even with a link to the matching PECL/PEAR entry rather then leaving the user in doubt if he/she can actually make use of the function in his/her environment.
Any comments/ideas how that could/should be done?
Steps we need to take to better handle PECL extensions:
- Move PECL extension docs from peardoc to PHPdoc (split as needed)
Analisys: I have checked those files, and some of them are there with a lot of CVS history which might not be a good idea to loose. So all 'en' files should be moved in the filesystem with history to phpdoc/en/functions (yes, the old dir, since these are files per extensions). Then Hartmut's split script should be executed on them (hope it will still work :).
Then the translated files could be moved by hand, since even phpdoc's own old one-file-per-extension files are not kept for translations...
That is means a small amount of work for systems@ :) :)) :))))
- Hartmut's function list script collection should be extended to handle PECL extensions and PECL version numbers, since this script collection generates the version information you have problems with. The most complicated part will probably be the handling of bundled extensions, since corresponding PECL / PHP version numbers need to be known...
Any objections with starting the first step (khm, with asking at systems@)?
Goba
