Zen

Source string Source string

76/10000 · 76

The string is read only.

English Actions
System services should store small volatile run-time data in `+/run+`. This is a tmpfs backed directory that is mounted in very early boot, before any services are started (and before `+/var+` is available). `+/var/run+` is a legacy symlink to `+/run+`.
No Files or Directories Under `+/srv+`, `+/usr/local+`, or `+/home/$USER+`
The https://www.pathname.com/fhs/pub/fhs-2.3.html#SRVDATAFORSERVICESPROVIDEDBYSYSTEM[FHS says]:
"...no program should rely on a specific subdirectory structure of /srv existing
or data necessarily being stored in /srv. However /srv should always exist on FHS
compliant systems and should be used as the default location for such data.
Distributions must take care not to remove locally placed files in these
directories without administrator permission."
The FHS is explicitly handing control of the directory structure under `+/srv+` to the system administrator rather than the distribution. Therefore, no Fedora packages can have any files or directories under `+/srv+`, come preconfigured to use specific files or directories under `+/srv+`, to remove files there, or to modify the files there in any way.
In addition, no Fedora package can contain files or directories or modify files under:
`+/usr/local+` as these directories are not permitted to be used by Distributions in the FHS
`+/home/$USER+` as users can arbitrarily modify the files in their home directories and rpm packages that modify those files run the risk of destroying user data. Additionally, sites may be nfs mounting `+/home+` on many different types of systems or even network automounting them on demand. Modifying files in home directories that are thus configured will have negative effects in both of these situations.
It is important to note that the software in a Fedora package, once installed and configured by a user, can use `+/srv+` as a location for data. The package simply must not do this out of the box
Limited Usage of `+/opt+`, `+/etc/opt+`, and `+/var/opt+`
`+/opt+` and its related directories (`+/etc/opt+` and `+/var/opt+`) is reserved for the use of vendors in the FHS. We have reserved the `+fedora+` name with https://www.lanana.org/lsbreg/providers/providers.txt[LANANA] for our use. If a package installs files into `+/opt+` it may only use directories in the `+/opt/fedora+` hierarchy. Fedora attempts to organize this directory by allocating a subdirectory of our `+/opt/fedora+` directory for specific subsystems. If you think you need to use `+/opt/fedora+` please file an FPC ticket to decide whether it's a valid use of `+/opt+` and what subdirectory should be allocated for your use.
Currently, we have allocated `+/opt/fedora/scls+`, `+/etc/opt/fedora/scls+`, and `+/var/opt/fedora/scls+` for use by {scl-guidelines}.
Because the Google-supplied Chrome packaging has chosen a specific file location for extension-specific files which, if used, would conflicts with the above guidelines, the Packaging Committee has approved the following exception: A package MAY install files into the `+/etc/opt/chrome/native-messaging-hosts+` directory, and may create that directory hierarchy, as long as package as a whole also supports Chromium. (The Chromium support MAY be in a different subpackage.) If Chrome in the future allows a more standard directory to be used for this purpose, this exception will be removed.
Merged file system layout
Fedora has merged several directories that historically used to be separate.
|Path|Merged with|RPM Macro

|`+/bin+`
|`+/usr/bin+`
|`+{_bindir}+`

|`+/sbin+`
|`+/usr/bin+`
|`+%{_bindir}+`

|`+/usr/sbin+`
|`+/usr/bin+`
|`+%{_bindir}+`

|`+/lib64+` or `+/lib+`
|`+/usr/lib64+` or `+/usr/lib+`
|`+%{_libdir}+`

|`+/lib+`
|`+/usr/lib+`
|`+%{_prefix}/lib+`
For example, end users will find that `+/bin/sh+` is the same file as `+/usr/bin/sh+`, and `+/usr/sbin/sendmail+` is the the same as `+/usr/bin/sendmail+`.
However, rpm file dependencies don't work according to what's on the filesystem, they work according to the path specified in the rpm `+%files+` section. So an rpm which specified:
%files
/bin/sh
would be able to satisfy a file dependency for `+/bin/sh+` but not for `+/usr/bin/sh+`. Packages **must** use the real filesystem paths in the `+%files+` section. If other packages have dependencies on a different path that resolves to the same file, and it is not convenient to update them to the new path, packages **may** use a virtual `+Provides+` to list the alternate path.
For instance:
Provides: /sbin/ifconfig
[...]
%files
%{_bindir}/ifconfig
Use `+rpmlint+`
Run rpmlint on binary and source rpms to examine them for common errors, and fix them (unless rpmlint is wrong, which can happen, too). If you find rpmlint's output cryptic, the `+-e+` switch to it can be used to get more verbose descriptions of most errors and warnings. Note that rpmlint will perform additional checks if given the name of an installed package. For example, `+dnf install foo-1.0-1.f20.x86_64.rpm; rpmlint -i foo+` will perform a set of tests on the foo package that `+rpmlint foo-1.0-1.f20.x86_64.rpm+` cannot. A community-maintained page on rpmlint issues can be found https://fedoraproject.org/wiki/Common_Rpmlint_issues[here].
Tags and Sections
The `+Copyright:+`, `+Packager:+`, `+Vendor:+` and `+PreReq:+` tags MUST NOT be used.
The `+BuildRoot:+` tag, `+Group:+` tag, and `+%clean+` section SHOULD NOT be used.
The contents of the buildroot SHOULD NOT be removed in the first line of `+%install+`.
The `+Summary:+` tag value SHOULD NOT end in a period.
The `+Source:+` tags document where to find the upstream sources for the package. In most cases this SHOULD be a complete URL to the upstream tarball. For special cases, please see the xref:SourceURL.adoc[SourceURL Guidelines].

Loading…

User avatar None

String added in the repository

  1. fedora-docs-l10n/packaging-guidelines
  2. master/pages/index
  3. English
Fedora has merged several directories that historically used to be separate.
Fedora has merged several directories that historically used to be separate.
2 days ago
Browse all string changes

Things to check

Multiple failing checks

Following checks are failing:
Mismatched colon: Portuguese (Brazil), Portuguese (Brazil)

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: Plain text
Flags
read-only
Source string location
./pages/index.adoc:648
String age
2 days ago
Last updated
2 days ago
Source string age
2 days ago
Translation file
pot/master/pages/index.pot, string 125