(New page: {{Draft}} == Changelog == * '''2009-01-30''': first shot = Existing Guideline = No guideline that would limit the use of hard links exists. == Proposal == Following change to Packagi...) |
(rpmlint patch) |
||
| Line 3: | Line 3: | ||
== Changelog == | == Changelog == | ||
* '''2009-01-30''': first shot | * '''2009-01-30''', 0.01: first shot | ||
* '''2009-01-30''', 0.02: add rpmlint patch | |||
= Existing Guideline = | = Existing Guideline = | ||
| Line 14: | Line 15: | ||
''If a file has more than one name, all names should be present in a single directory. Hard links that span multiple directories are prohibited, since they will make it impossible to install a package in setups where the directories reside on different file systems.'' | ''If a file has more than one name, all names should be present in a single directory. Hard links that span multiple directories are prohibited, since they will make it impossible to install a package in setups where the directories reside on different file systems.'' | ||
A patch to rpmlint [http://rpmlint.zarb.org/cgi-bin/trac.cgi/ticket/171] exists that would help packagers find out where do they break this proposed guideline. | |||
== Motivations == | == Motivations == | ||
Revision as of 07:44, 30 January 2009
It is still under construction and content may change. Do not rely on the information on this page.
Changelog
- 2009-01-30, 0.01: first shot
- 2009-01-30, 0.02: add rpmlint patch
Existing Guideline
No guideline that would limit the use of hard links exists.
Proposal
Following change to Packaging Guidelines is proposed: Add a section Use of Hard Links which would read:
If a file has more than one name, all names should be present in a single directory. Hard links that span multiple directories are prohibited, since they will make it impossible to install a package in setups where the directories reside on different file systems.
A patch to rpmlint [1] exists that would help packagers find out where do they break this proposed guideline.
Motivations
The wording of the paragraph above pretty much explains the motivation. The example where this caused problems is [2].
Existing practice
TBD: Determine which packages currently use hard links in a manner which would conflict with this guideline.