From Fedora Project Wiki
< Changes
(Created page with "= Drop php-pear dependency for pecl modules = == Summary == All PECL packaged modules (php-pecl-*) have a unneeded dependency on php-pear, for module registration in package ...") |
|||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
== Summary == | == Summary == | ||
All PECL packaged modules (php-pecl-*) have a unneeded dependency on php-pear, for module registration in package | All PECL packaged modules (php-pecl-*) have a unneeded runtime dependency on php-pear, for module registration in package scriptlets. | ||
== Owner == | == Owner == | ||
| Line 24: | Line 24: | ||
CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | CLOSED as NEXTRELEASE -> change is completed and verified and will be delivered in next release under development | ||
--> | --> | ||
* Tracker bug: | * Tracker bug: [https://bugzilla.redhat.com/show_bug.cgi?id=1310546 #1310546] | ||
Status: | |||
* New %{pecl_xmldir} directory defined and owned by php-common: Done | |||
* New file triggers in php-pear: Done | |||
* PHP Guidelines changes: FPC approved | |||
== Detailed Description == | == Detailed Description == | ||
| Line 39: | Line 44: | ||
* drop runtime dependency on php-pear | * drop runtime dependency on php-pear | ||
* fix circular dependencies (php-cli => php-common => php-pecl-jsonc => php-pear => php-cli) | * fix circular dependencies (php-cli => php-common => php-pecl-jsonc => php-pear => php-cli) | ||
* no more "API" warning on version update (will be useful for 5.6 / 7.0 upgrade), as the registration is now executed at the end of the transaction | * no more "API" warning on version update (will be useful for 5.6 / 7.0 upgrade using fedup), as the registration is now executed at the end of the transaction | ||
== Scope == | == Scope == | ||
| Line 48: | Line 52: | ||
<!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do the feature owners have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Other developers: cleanup pecl module, not mandatory (scriptlets are now noop) | * Other developers: | ||
** cleanup pecl module, not mandatory (scriptlets are now noop) | |||
<!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | <!-- What work do other developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?--> | ||
* Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Release engineering: N/A (not a System Wide Change) <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
<!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | <!-- Please check the list of Fedora release deliverables and list all the differences the feature brings --> | ||
* Policies and guidelines: https://fedorahosted.org/fpc/ticket/597 <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | * Policies and guidelines: | ||
** https://fedorahosted.org/fpc/ticket/597 <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | |||
<!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | <!-- Do the packaging guidelines or other documents need to be updated for this feature? If so, does it need to happen before or after the implementation is done? If a FPC ticket exists, add a link here. --> | ||
| Line 72: | Line 76: | ||
== How To Test == | == How To Test == | ||
<!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. | <!-- This does not need to be a full-fledged document. Describe the dimensions of tests that this change implementation is expected to pass when it is done. If it needs to be tested with different hardware or software configurations, indicate them. The more specific you can be, the better the community testing can be. --> | ||
* Install php and some pecl packages | * Install php and some pecl packages | ||
* | * Install php-pear | ||
* run pecl list to check registered extensions | * run "pecl list" to check registered extensions | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
== User Experience == | == User Experience == | ||
| Line 119: | Line 122: | ||
[[Category: | [[Category:ChangeAcceptedF24]] | ||
<!-- When your change proposal page is completed and ready for review and announcement --> | <!-- When your change proposal page is completed and ready for review and announcement --> | ||
<!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | <!-- remove Category:ChangePageIncomplete and change it to Category:ChangeReadyForWrangler --> | ||
Latest revision as of 12:05, 4 May 2016
Drop php-pear dependency for pecl modules
Summary
All PECL packaged modules (php-pecl-*) have a unneeded runtime dependency on php-pear, for module registration in package scriptlets.
Owner
- Name: Remi Collet
- Email: php-devel@fedoraproject.org
- Release notes owner:
Current status
Status:
- New %{pecl_xmldir} directory defined and owned by php-common: Done
- New file triggers in php-pear: Done
- PHP Guidelines changes: FPC approved
Detailed Description
Each pecl module package uses scriptlet which use the pecl command, so requires php-pear at runtime.
php-pear is a dying project, and most of users don't need/want it.
Replace the scriptlets in pecl package by file triggers in the php-pear package.
Benefit to Fedora
This fix various annoying bugs:
- drop runtime dependency on php-pear
- fix circular dependencies (php-cli => php-common => php-pecl-jsonc => php-pear => php-cli)
- no more "API" warning on version update (will be useful for 5.6 / 7.0 upgrade using fedup), as the registration is now executed at the end of the transaction
Scope
- Proposal owners:
- Replace the scriptlets in pecl package by file triggers in the php-pear package.
- Other developers:
- cleanup pecl module, not mandatory (scriptlets are now noop)
- Release engineering: N/A (not a System Wide Change)
- Policies and guidelines:
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
Users will be able to use PHP and pecl module without php-pear.
If php-pear is installed, module will be registered as previously.
How To Test
- Install php and some pecl packages
- Install php-pear
- run "pecl list" to check registered extensions
User Experience
They should not notice any change.
Dependencies
- php-pecl-*
Contingency Plan
- Contingency mechanism:
- Not needed, could be fixed if needed, but module regsitration is only there for users (not for packaging needs).
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? No
Documentation
Will be in the PHP packaging guidelines.
Release Notes
TBD