From Fedora Project Wiki

< Changes

Revision as of 06:52, 16 July 2013 by Akozumpl (talk | contribs) (Created page with "{{admon/important | Comments and Explanations | The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To re...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Important.png
Comments and Explanations
The page source contains comments providing guidance to fill out each section. They are invisible when viewing this page. To read it, choose the "edit" link.
Copy the source to a new page before making changes! DO NOT EDIT THIS TEMPLATE FOR YOUR CHANGE PROPOSAL.


Change Proposal Name

Summary

Disallow dependencies on files under /bin, /sbin, /lib and /lib64.

Owner

Current status

  • Targeted release: Fedora 20
  • Last updated: (DATE)
  • 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.

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:
  • 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: (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

Documentation

N/A (not a System Wide Change)

Release Notes