Revision as of 09:50, 10 February 2016

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 scriptlet.

Owner

Name: Remi Collet
Email: php-devel@fedoraproject.org
Release notes owner:

Current status

Targeted release: Fedora 24
Last updated: 2016-02-10
Tracker bug: <will be assigned by the Wrangler>

Status:

New %{pecl_xmldir] directory defined and owned by php-comm: Done
New file triggers in php-pear: Done
PHP Guidelines changes: FPC submitted

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), 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:
- https://fedorahosted.org/fpc/ticket/597

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

TBD

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

@@ Line 53: / Line 53: @@
 <!-- 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?-->
 * Release engineering: N/A (not a System Wide Change)  <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
-** [[Fedora_Program_Management/ReleaseBlocking/Fedora{{FedoraVersionNumber|next}}|List of deliverables]]: 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 -->
-* Policies and guidelines: https://fedorahosted.org/fpc/ticket/597 <!-- REQUIRED FOR SYSTEM WIDE CHANGES -->
+* Policies and guidelines:
-** introduce a change to Python packaging guidelines for package maintainers to be able to profit from this change (after the implementation is ready)
+** 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. -->

Search

Changes/drop pear dep: Difference between revisions