|
|
| (2 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| {{draft}} | | {{draft}} |
| = Current =
| |
|
| |
| == Filesystem Layout == | | == Filesystem Layout == |
|
| |
|
| Fedora follows the [http://www.pathname.com/fhs/ Filesystem Hierarchy Standard (FHS)] with regards to filesystem layout. The FHS defines where files should be placed on the system. Fedora packages must follow the FHS. Any deviation from the FHS should be rationalized when the package is reviewed. | | Fedora follows the [http://www.pathname.com/fhs/ Filesystem Hierarchy Standard] with regards to filesystem layout, with exceptions noted below. The FHS defines where files should be placed on the system. |
| | |
| {{admon/note||Some interpretations of the FHS say that the FHS does not prevent distributions from creating and using directories outside of the listed hierarchies (for instance, adding new toplevel directories to <code>/</code> or adding new directories under <code>/usr</code>). For the purposes of the Fedora Packaging Guidelines, new directories of this sort are not allowed unless listed in the Guidelines. If you feel the need for a new directory, please contact the FPC with a rationale for the directory and what category of software belongs in that directory. You may need to read the FHS to tell if a directory is already part of an FHS approved hierarchy.}}
| |
| | |
| There are notable exceptions to this guideline for libexecdir (as specified in the [http://www.gnu.org/prep/standards/standards.html#index-libexecdir-139 GNU Coding Standards]), <code>/run</code> (which has been widely adopted by Linux distributions even though a new version of the FHS has not been released that includes it) and /usr/target for cross-compilers.
| |
| | |
| {{Anchor|libexecdir}}
| |
| === Libexecdir ===
| |
| | |
| The [http://www.pathname.com/fhs/ Filesystem Hierarchy Standard] does not include any provision for libexecdir, but Fedora packages may store appropriate files there. Libexecdir (aka, <code>/usr/libexec</code> on Fedora systems) should only be used as the directory for executable programs that are designed primarily to be run by other programs rather than by users.
| |
| | |
| | |
| = Proposed =
| |
| | |
| | |
| == Filesystem Layout ==
| |
| | |
| Fedora follows the [http://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.txt Filesystem Hierarchy Standard version 3.0 (FHS-3.0)] with regards to filesystem layout. The FHS defines where files should be placed on the system. Fedora packages must follow the FHS. Any deviation from the FHS should be rationalized when the package is reviewed.
| |
| | |
| {{admon/note||Some interpretations of the FHS say that the FHS does not prevent distributions from creating and using directories outside of the listed hierarchies (for instance, adding new toplevel directories to <code>/</code> or adding new directories under <code>/usr</code>). For the purposes of the Fedora Packaging Guidelines, new directories of this sort are not allowed unless listed in the Guidelines. If you feel the need for a new directory, please contact the FPC with a rationale for the directory and what category of software belongs in that directory. You may need to read the FHS to tell if a directory is already part of an FHS approved hierarchy.}}
| |
| | |
| There is a notable exceptions to this guideline for /usr/target (used for cross-compilers).
| |
|
| |
|
| {{Anchor|libexecdir}}
| | === Exceptions === |
| === Libexecdir === | |
|
| |
|
| The [http://refspecs.linuxfoundation.org/FHS_3.0/fhs-3.0.txt Filesystem Hierarchy Standard version 3.0] (unlike previous versions) does include provision for libexecdir, and Fedora packages may store appropriate files there. Libexecdir (aka, <code>/usr/libexec</code> on Fedora systems) should only be used as the directory for executable programs that are designed primarily to be run by other programs rather than by users.
| | * Fedora allows cross-compilers to place files in <code>/usr/target</code>. |
|
| |
|
| | * Fedora does not allow new directories directly under <code>/</code> or <code>/usr</code> without FPC approval. |
|
| |
|
| [[Category:Packaging guidelines drafts]] | | [[Category:Packaging guidelines drafts]] |
