If upstream ships filenames that aren't encoded in UTF-eight You should utilize a utility like convmv (through the convmv bundle) to transform the filename inside your %put in portion. Spec Upkeep and Canonicity
You can find very little benefit in selecting one style above the other, since they may resolve to a similar values in all scenarios. You ought to pick a type and utilize it persistently all over your packaging.
Marking a relative route with %doc while in the %files section will lead to RPM to repeat the referenced file or Listing from %_builddir to the appropriate location for documentation. Documents can even be placed in %_pkgdocdir, as well as the Construct scripts of the computer software staying packaged may do that routinely when referred to as in %install.
The %defattr directive during the %data files list SHOULD ONLY be applied when environment a non-default price, or to reset into the default value following acquiring set a non-default benefit. People and Teams
All other info in the customer phase of the Mixed Load Label shall be specified by The client including customer P.O. and read review line variety.
Information still has to be reviewed for inclusion. It needs to have an open up supply suitable license, ought to not be legally questionable. Moreover, there are numerous further restrictions for information:
The devel subpackage need to have a Digital Supply with the *-static offer, and deals depending on it must BuildRequire the *-static package.
Additionally, in some cases, aged specific dependencies on package names require unnecessary updates/rebuilds. As an example, Fedora offers are only needed to retain historic offers for two total launch cycles.
Overpackaging and wasteful “just just in case” packaging is unwanted for each the provider and also the user.
Permissions on information Needs to be established correctly. Within /usr, data files should be owned by root:root Except a more certain consumer or team is needed for safety.
If that fails as a result of unwilling or unresposive upstream, the packager may perhaps start versioning downstream but this should be accomplished with caution and ideally only in unusual circumstances.
Static libraries and shared libraries. In this instance, the static libraries MUST be put in a very *-static subpackage. Separating the static libraries from the other enhancement information in *-devel let us to track this use by examining which deals BuildRequire the *-static package.
– Plastic and metal banding have to be used employing suitable stress settings. Too much pressure can cause container failure and inadequate load containment and also pallet failure.
For those who feel that your package deal needs to be exempt from A part of the Guidelines, you should provide The difficulty to the Fedora Packaging Committee.