[snip] > From my understanding is that a lot of stuff that resides currently > in ext/ will be moved to PECL, so when version 5.1 comes out what > will we do in that case? [/snip]
In light of this good point the following is a more flexible approach. I believe the following format will meet all possible conditions (except one) like newly introduced PECL extensions, extensions that are bundled or not, and whether or not it's in PHP 4. What do you guys think? A PHP 8 PECL extension would be fine too. The one condition that's a problem is where to find a PECL extension that's in PHP 4 yet not bundled with the PHP 4 Windows binaries. There isn't really an official place to get these except at snaps.php.net so we can deal with this later. If eventually offered at pecl.php.net then the &pecl.info; entity covers this. Most of this information should be listed at pecl.php.net anyways! If not then we could add an additional download source to the &pecl.windows.4; entity (like snaps) or a new entity. The entities themselves can use some touchup/rewording but the ideas are what's most important here, feel free to offer opinions on both. Again, using ref.crack as an example: from configure.xml --------------------------- <para> &pecl.moved; (or &pecl.bundled;) &pecl.info; (always used) <ulink url="&url.pecl.package;crack">&url.pecl.package;crack</ulink>. </para> <para> &pecl.source.4; (no alternative entity) In order to use these functions you must compile PHP with Crack support by using the <option role="configure">--with-crack[=DIR]</option> option. </para> <para> Windows users will enable <filename>php_crack.dll</filename> inside of &php.ini; in order to use these functions. &pecl.windows.4 (maybe offer an additional source for non-bundled) &pecl.windows.download; (always used) </para> from language-snippets.ent --------------------------- <!ENTITY pecl.moved 'This <ulink url="&url.pecl;">PECL</ulink> extension is not bundled with PHP.'> <!ENTITY pecl.bundled 'This <ulink url="&url.pecl;">PECL</ulink> extension is bundled with PHP.'> <!ENTITY pecl.info 'Additional information such as new releases, downloads, source files, maintainer information, and a CHANGELOG, can be located here: '> <!ENTITY pecl.source.4 'In PHP 4 this <acronym>PECL</acronym> extension's source can be found in the <filename>ext/</filename> directory within the PHP source or at the <acronym>PECL</acronym> link above.'> <!ENTITY pecl.windows.4 'In PHP 4 this <acronym>DLL</acronym> resides in the <filename>extensions/</filename> directory within the PHP Windows binaries download.'> <!ENTITY pecl.windows.download 'You may download PECL extension <acronym>DLL</acronym>'s from the <ulink url="&url.php.downloads;">PHP Downloads</ulink> page.'> > Now after thinking about it, mabey if we can find a nice solution > with the documentation's changelog (as you previously mentioned). > These items could go there, and would be really nice if the > function could reference that changelog somehow. Not sure about using CHANGELOG for this, let's see how the above approach looks. I like it because it would go in configure.xml and use a lot of entities. Regards, Philip
