If none of the file attributes filemode, username, and groupname are populated, the defaults defaultFileMode , defaultUsername , defaultGroupname , and defaultDirmode will be used.
This is UNIX permissions file mode to assign to directories when installed. Each digit represents the access allowed and is the sum of 4 for read, 2 for write, and 1 for execute in the context of directories, 'execute' allows the user to list the contents of the directory. Everyone is allowed to list the contents of the directory. If not specified, filemode, will be used instead. This property is useful if you want files and directories included in a single mapping to have different permissions.
The canonical example would be files that are readable and directories that have the executable bit set That way, the directories can be listed, but the files remain non-executable.
If none of the file attributes dirmode, filemode, username, and groupname are populated, the defaults defaultFileMode , defaultUsername , defaultGroupname , and defaultDirmode will be used. This is the UNIX username to assign to the files when installed.
If the named user does not exist when the package is installed, the user root will be used. If not specified, the files will be owned by the user used to create the package. This is the UNIX groupname to assign to the files when installed. If the named group does not exist when the package is installed, the group root will be used. If not specified, the files will be owned by the group used to create the package. Additional context can be supplied using Requires qualifier syntax, accepted qualifiers are:.
Denotes the dependency must be present in before the package is is installed, and is used a strong ordering hint to break possible dependency loops. A pre-dependency is free to be removed once the install-transaction completes. Denotes the dependency must be present right after the package is is installed, and is used a strong ordering hint to break possible dependency loops. A post-dependnecy is free to be removed once the install-transaction completes.
Denotes the dependency must be present in before the package is is removed, and is used a strong ordering hint to break possible dependency loops. Denotes the dependency must be present right after the package is is removed, and is used a strong ordering hint to break possible dependency loops. Denotes the dependency must be present before the transaction starts, and cannot be satisified by added packages in a transaction.
As such, it does not affect transaction ordering. A pretrans-dependency is free to be removed after the install-transaction completes. Denotes the dependency must be present at the end of transaction, ie cannot be removed during the transaction.
A posttrans-dependency is free to be removed after the the install-transaction completes. Denotes a scriptlet interpreter dependency, usually added automatically by rpm. Used as a strong ordering hint for breaking dependency loops. Typical use-cases would be meta-packages and sub-package cross-dependencies whose purpose is just to ensure the sub-packages stay on common version.
As noted above, dependencies qualified as install-time only pretrans , pre , post , posttrans or combination of them can be removed after the installation transaction completes if there are no other dependencies to prevent that.
This is a common source of confusion. Capabilities this package conflicts with, typically packages with conflicting paths or otherwise conflicting functionality.
Package is not buildable on architectures listed here. Used when software is portable across most architectures except some, for example due to endianess issues. Package is only buildable on architectures listed here. Specifies the architecture which the resulting binary package will run on. Typically this is a CPU architecture like sparc, i Typical platform independent packages are html, perl, python, java, and ps packages.
As a special case, BuildArch: noarch can be used on sub-package level to allow eg. Specify prefixes this package may be installed into, used to make packages relocatable.
Very few packages are. However, this convention results in "dst" always being the file that is created when installing the package. From the RPM directives documentation: "There are times when a file should be owned by the package but not installed - log files and state files are good examples of cases you might desire this to happen.
By adding this directive to the line containing a file, RPM will know about the ghosted file, but will not add it to the package. When building RPMs, however, this type has another important purpose: Claiming ownership of that folder. This is important because when upgrading or removing an RPM package, only the directories for which it has claimed ownership are removed.
0コメント