Normally, it shouldn't be needed for several offers to have equivalent copies of precisely the same file. On the other hand, if it's important, a number of packages could consist of identical copies of exactly the same file, as long as the following necessities are met:
Until you need to use people outside the house the ASCII repertoire , you won't need to be worried about the encoding on the spec file.
/bin/sh might be able to satisfy a file dependency for /bin/sh but not for /usr/bin/sh. Like a packager you may need to concentrate to exactly where other deals look forward to finding your files. Things that heritage has put into /bin, /sbin, /lib, or /lib64 should be listed in the %documents area as getting in All those directories.
Mixing the two kinds, whilst legitimate, is lousy from the QA and usability perspective, and really should not be carried out in Fedora deals.
For anyone who is Uncertain if a little something is taken into account accepted content material, talk to on fedora-devel-list. Offers which are not handy without the need of external bits
Bootstrapped deals containing pre-constructed "bootstrap" binaries should not be pushed as launch offers or updates below any circumstances. These packages should really incorporate the mandatory logic to get crafted at the time bootstrapping is finished plus the prebuilt plans are no more essential. Information regarding how you'll want to crack round dependencies by bootstrapping are available below: Packaging:Guidelines#Bootstrapping
If a package deal to become imported is or Earlier was present inside a publicly accessible repository, the packager can optionally incorporate an Epoch tag equivalent to that of the most recent Edition of the 3rd-social gathering deal. Symlinks
The bulk of such packaging guidelines includes what goes into a spec, but here are a few general items. Spec File Naming
The identical applies to reviewers/testers. Rebuild src.rpms in the separate account which does not have access to any sensitive knowledge. Relocatable packages
A versioned dependency on the deal with a defined Epoch Have to be A part of that dependency. If not the dependency will never functionality as anticipated. Your Domain Name Architecture-distinct Dependencies
Thus, no Fedora deals might have any information or directories under /srv, occur preconfigured to utilize specific data files or directories below /srv, to get rid of data files there, or to switch the documents there in almost any way.
You are able to do this any quantity of situations, until finally you really Develop one.0-1 while in the buildsystem. When you've completed that, you have to alter the E-V-R and any new entries needs to be extra as described in Changelogs. Repeat the old Variation release with a new entry
Observe: A unit that falls below several categories needs to be prepped In line with all applicable prep forms. One example is, If you're advertising bottles of Shampoo and Conditioner being a set, equally units will require to meet the Liquid specifications and be labeled which has a "Marketed as Established" sticker so that they are not divided.
compilers generally include things like enhancement data files in the leading deal mainly because compilers are by themselves only employed for application growth, As a result, a split package deal model isn't going to make any feeling.