From Fedora Project Wiki
< Changes
No edit summary |
(Moving to incomplete pages due to FESCo resolution as FPC item) |
||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 21: | Line 21: | ||
<!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | <!-- The actual name of your proposed change page should look something like: Changes/Your_Change_Proposal_Name. This keeps all change proposals in the same namespace --> | ||
= Change | = Change Packaging Guidelines to discourage requires into /bin and /sbin = | ||
== Summary == | == Summary == | ||
| Line 60: | Line 60: | ||
Whenever possible you should avoid file dependencies outside of /etc, /usr/bin, or /usr/sbin. | Whenever possible you should avoid file dependencies outside of /etc, /usr/bin, or /usr/sbin. | ||
Related FPC ticket https://fedorahosted.org/fpc/ticket/314, FPC wanted this change to be created. | |||
== Benefit to Fedora == | == Benefit to Fedora == | ||
| Line 69: | Line 71: | ||
<!-- What work do the developers have to accomplish to complete the change 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 developers have to accomplish to complete the change 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?--> | ||
* Proposal owners: | * Proposal owners: None | ||
<!-- 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?--> | ||
| Line 125: | Line 127: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
This. | This proposal and the Fedora Packaging Guidelines. | ||
== Release Notes == | == Release Notes == | ||
| Line 141: | Line 143: | ||
<!-- Select proper category, default is Self Contained Change --> | <!-- Select proper category, default is Self Contained Change --> | ||
[[Category:SystemWideChange]] | [[Category:SystemWideChange]] | ||
[[Category: | [[Category:ChangePageIncomplete]] | ||
Latest revision as of 13:57, 18 November 2013
Change Packaging Guidelines to discourage requires into /bin and /sbin
Summary
Disallow dependencies on files under /bin, /sbin, /lib and /lib64.
Owner
- Name: Ales Kozumplik
- Email: ales@redhat.com
- Release notes owner:
Current status
- Targeted release: Fedora 20
- Last updated: July 16, 2013.
- Tracker bug: <will be assigned by the Wrangler>
Detailed Description
The current packaging guidelines read:
Whenever possible you should avoid file dependencies outside of /etc, /bin, /sbin, /usr/bin, or /usr/sbin.
I propose changing this to:
Whenever possible you should avoid file dependencies outside of /etc, /usr/bin, or /usr/sbin.
Related FPC ticket https://fedorahosted.org/fpc/ticket/314, FPC wanted this change to be created.
Benefit to Fedora
Making the UsrMove business a bit less unfinished. /bin dependencies etc. don't currently work for dependency resulition properly anyway, there's nothing providing e.g. /bin/python, even though the two paths are accidentally the same in today's Fedora.
Scope
- Proposal owners: None
- Other developers: replace all explicit /bin/<foo> requires with /usr/bin/<foo>.
- Release engineering: N/A
- Policies and guidelines: update the packaging guidelines accordingly.
Upgrade/compatibility impact
Packages with broken /bin requires will be installable again once they are fixed.
How To Test
Packaging guidelines contain information that /bin etc. requires should be avoided.
User Experience
End users will not notice.
Dependencies
None.
Contingency Plan
- Contingency mechanism: FPC changing the guideline.
- Contingency deadline: Anytime.
- Blocks release? No.
Documentation
This proposal and the Fedora Packaging Guidelines.