No edit summary |
(adde versioned requires section) |
||
| Line 24: | Line 24: | ||
Noticed [[Packaging/Guidelines#tags]] has 2 broken links to www.rpm.org | Noticed [[Packaging/Guidelines#tags]] has 2 broken links to www.rpm.org | ||
== Versioned Requires == | |||
Guideline states | |||
Second, the Epoch must be listed when adding a versioned dependency to achieve robust epoch-version-release comparison. A quick way to check the Epoch of package foo is to run: | |||
rpm --query --qf "%{EPOCH}\n" packagename | |||
However, if this returns (null), the package has no epoch. Therefore Requires: cannot include an epoch. | |||
Revision as of 14:24, 13 October 2009
Broken internal links
Exceptions is used as an id to an <a> tag twice, and as a result, the two different links to #Exceptions (which should be different) do not work properly.
Look for string ",so" and change it to ".so".
libs subpackages
Should there be some info on naming / reasons for having -libs subpackages in here somewhere?
Layout update.
In "Packaging Static Libraries" Could we get a layout update so that the points 1 and 2 both start on new lines.
Patch Upstream Status
Is this a Guideline? I guess so, because it is in the Packaging Namespace, but it is only linked from PackageMaintainers/CreatingPackageHowTo
Packaging/PatchUpstreamStatus --Till 10:40, 8 August 2008 (UTC)
Noticed Packaging/Guidelines#tags has 2 broken links to www.rpm.org
Versioned Requires
Guideline states Second, the Epoch must be listed when adding a versioned dependency to achieve robust epoch-version-release comparison. A quick way to check the Epoch of package foo is to run:
rpm --query --qf "%{EPOCH}\n" packagename
However, if this returns (null), the package has no epoch. Therefore Requires: cannot include an epoch.