portgroups for php5 extensions

[ryandesign (Ryan Carsten Schmidt)]

There are many similarities in the php5-* PECL ports (e.g. php5-eaccelerator, php5-apc, php5-yaz, php5-xdebug, etc.) that could be brought out into a new portgroup, which should probably be called pecl.

[ryandesign (Ryan Carsten Schmidt)]

I now think the portgroup should be called php5pecl. The portgroup will need to declare a dependency on the php5 port. And there will come a day when there is a php6 and we need to have module ports for it. It is also consistent with other existing portgroups (perl5, python30) to include the major version number in the portgroup name.

There will also be another portgroup, which might be called php5 or php5ext, for modules that are part of the base php source. I think it's good to begin both of these related portgroup names with the prefix "php5".

[ryandesign (Ryan Carsten Schmidt)]

Initial version of php5pecl committed in r49692. There are more changes to come.

[ryandesign (Ryan Carsten Schmidt)]

• r49694: switch wording to "extension" and set up php5pecl.extension and php5pecl.extension_dir
• r49695: post-install ui_msgs

[ryandesign (Ryan Carsten Schmidt)]

• r49698: set up php5pecl.homepage and livecheck

[ryandesign (Ryan Carsten Schmidt)]

• r49700: php5-yaz is the first port to use php5pecl

[ryandesign (Ryan Carsten Schmidt)]

• r49711: remove php5pecl.extension_dir for now; it broke the portindex because php-config obviously cannot be called unless php5 is installed
• r50161: php5pecl has been removed and replaced with two new portgroups, php5extension and php5peclextension, in recognition of the fact that not all php modules are hosted on pecl

[ryandesign (Ryan Carsten Schmidt)]

• r50173: php ports now look for additional .ini files in ${prefix}/var/db/php${major}
• r50175: php5extension portgroup now creates an .ini file for each extension in that directory; bump revision of php5-yaz to get this change

[(none)]

Milestone Port Enhancements deleted

[ryandesign (Ryan Carsten Schmidt)]

Anthony made these changes:

• r50183: php5-apc: use php5peclextension portgroup
• r50184: php5-http: use php5peclextension portgroup
• r50185: php5-intl: use php5peclextension portgroup
• r50187: php5-sqlite3: use php5peclextension portgroup
• r50188: php5-uploadprogress: use php5peclextension portgroup

Olivier made these changes:

• r50191: php5-eaccelerator: use php5extension portgroup

I made these changes:

• r50357: php5-syck: use php5extension portgroup
• r50364: php5-memcache: use php5peclextension portgroup
• r50436: merge php5peclextension functionality into php5extension portgroup
• r50437: php5-yaz: switch to php5extension portgroup
• r50438: php5-memcache: switch to php5extension portgroup
• r50439: php5-intl, php5-uploadprogress, php5-http, php5-apc, php5-sqlite3: switch to php5extension portgroup
• r50440: remove php5peclextension portgroup
• r50444: accommodate extensions which are not PHP extensions but Zend extensions
• r50446: php5-xdebug: use php5extension portgroup

I think this ticket can be closed now.

[danocd@…]

Why not to add suhosin to this portgroup?

[ryandesign (Ryan Carsten Schmidt)]

Because I forgot we had a suhosin port, because its name does not begin with the customary "php5-" prefix.

Please file a separate ticket for any remaining ports that should be moved to this portgroup.