The Greatest Guide To Standards And Packaging Guidelines
Technique products and services need to shop smaller risky operate-time details in /run. This can be a tmpfs backed Listing that's mounted in pretty early boot, right before any providers are commenced (and ahead of /var is offered).
An illustration situation when /not/ to use noreplace is whenever a package deal's configuration file alterations so which the new deal revision wouldn't operate Along with the config file through the prior package revision. Every time plain %config is applied, include a brief remark on the specfile conveying why.
Fedora's git repository may be the canonical location for Fedora spec data files. Maintainers Need to assume that other maintainers and automatic tooling will make alterations for their packages, perhaps with out speaking previous to doing this (however conversation is usually encouraged).
Deals ought to produce useful -debuginfo offers, or explicitly disable them when it can be impossible to generate a practical one particular but rpmbuild would do it anyway.
Fedora offers should be intended with a rational separation of data files. Especially, -devel deals have to be utilized to incorporate data files which might be intended exclusively for development or required only at Establish-time.
It might be tempting to produce the header library bundle noarch, Because the header documents on their own are merely textual content. However, a library must have assessments which should be operate on all architectures.
– Acceptable Hundreds The guidelines beneath are determined by handbook content dealing with approaches which permit the offer to generally be carried near the body and which tend not to need excessive bending or squatting:
Translation data files might be handled by distinct courses for various frameworks. Make sure you add BuildRequires: for the right package deal or else your deal could fall short to create translation data files during the buildroot.
– Strapping really should be applied only Source in vertical alignment. The usage of horizontal banding is a bad packaging observe and should require an update on the corrugated paperboard and/or even the addition of corner supports.
A versioned dependency with a package with a defined Epoch Should be A part of that dependency. If not the dependency will not perform as predicted. Architecture-specific Dependencies
The summary ought to be a brief and concise description of your deal. The outline expands upon this. Tend not to include installation Recommendations in the description; It is far from a manual. Should the bundle necessitates some manual configuration or there are other crucial Directions to the person, refer the consumer to the documentation within the bundle.
The usage of RPM's facility for building relocatable deals is strongly discouraged. It is actually challenging to make do the job thoroughly, unachievable to make use of with the installer or from yum, instead of generally important if other packaging guidelines are followed.
/var is supposed to incorporate variable information files and logs. /usr/share is considerably more appropriate for this.
They must in no way just consist of an entire copy with the resource CHANGELOG entries. The intent is to give the user a hint concerning what altered in a very offer update with out overpowering them Using the specialized information. Hyperlinks to upstream changelogs could be entered for many who want more facts.