From Fedora Project Wiki
< Changes
No edit summary |
(Moving to incomplete pages due to FESCo resolution as FPC item) |
||
| (7 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 41: | Line 41: | ||
== Current status == | == Current status == | ||
* Targeted release: [[Releases/20 | Fedora 20 ]] | * Targeted release: [[Releases/20 | Fedora 20 ]] | ||
* Last updated: | * Last updated: July 16, 2013. | ||
<!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | <!-- After the change proposal is accepted by FESCo, tracking bug is created in Bugzilla and linked to this page | ||
Bugzilla states meaning as usual: | Bugzilla states meaning as usual: | ||
| 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 115: | Line 117: | ||
== Contingency Plan == | == Contingency Plan == | ||
<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | <!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "Revert the shipped configuration". Or it might not (e.g. rebuilding a number of dependent packages). If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. --> | ||
* Contingency mechanism: | * Contingency mechanism: FPC changing the guideline. | ||
<!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | <!-- When is the last time the contingency mechanism can be put in place? This will typically be the beta freeze. --> | ||
* Contingency deadline: | * Contingency deadline: Anytime. | ||
<!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | <!-- Does finishing this feature block the release, or can we ship with the feature in incomplete state? --> | ||
* Blocks release? | * Blocks release? No. | ||
== Documentation == | == Documentation == | ||
| Line 125: | Line 127: | ||
<!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | <!-- REQUIRED FOR SYSTEM WIDE CHANGES --> | ||
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.