< Changes
mNo edit summary |
No edit summary |
||
| Line 151: | Line 151: | ||
<!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | <!-- What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this change depends? In other words, completion of another change owned by someone else and might cause you to not be able to finish on time or that you would need to coordinate? Other upstream projects like the kernel (if this is not a kernel change)? --> | ||
< | Need to patch pkgconfig dependency generator in <code>rpm</code> and possibly add some macro in <code>redhat-rpm-config</code> package. | ||
== Contingency Plan == | == Contingency Plan == | ||
Revision as of 20:35, 12 August 2018
Stop pulling dependencies for static libraries
Summary
Since day 0, RPM dependency generator for pkg-config files was pulling in both Requires and Requires.private. We will change generator to pull Requires.private only if static library is actually packaged.
Owner
- Name: Igor Gnatenko
- Email: ignatenkobrain@fedoraproject.org
- Release notes owner:
Current status
- Targeted release: Fedora 30
- Last updated: 2018-08-12
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
Requires.private is only used when using pkg-config --static to link statically. Most of the packages in fedora don't ship static libraries and Packaging Guidelines discourage packaging them.
The idea is to make them conditional by using rich dependencies which will change things like pkgconfig(x11) to (pkgconfig(x11) if pkgconfig-static(gdk-3.0)).
Alternatively/Additionally we could do a switch which will make generator to not generate such requirements.
Benefit to Fedora
This change makes dependency chain of -devel packages providing pkg-config smaller and additionally make metadata smaller.
Scope
- Proposal owners: Adjust dependency generator to do the right thing, update packaging guidelines.
- Other developers: Package maintainers which ship static library will need to update their packages with new packaging policy.
- Release engineering: #Releng issue number (a check of an impact with Release Engineering is needed)
- List of deliverables: N/A (not a System Wide Change)
- Policies and guidelines: Guidelines need to be updated (not more that 1-2 paragraphs).
- Trademark approval: N/A (not needed for this Change)
Upgrade/compatibility impact
dnf autoremove will remove useless packages from end-user systems. Users might be confused by that.
How To Test
TBD.
User Experience
See "Benefit to Fedora"
Dependencies
Need to patch pkgconfig dependency generator in rpm and possibly add some macro in redhat-rpm-config package.
Contingency Plan
- Contingency mechanism: (What to do? Who will do it?) N/A (not a System Wide Change)
- Contingency deadline: N/A (not a System Wide Change)
- Blocks release? N/A (not a System Wide Change), Yes/No
- Blocks product? product
Documentation
TBD.