mirror of
https://github.com/YellowJacketLinux/LFS.git
synced 2025-02-02 23:07:14 +08:00
started work
This commit is contained in:
parent
50c716849e
commit
81b02bdb9f
@ -1,4 +1,24 @@
|
|||||||
The %{?repo} Tag
|
The %{?repo} Tag
|
||||||
================
|
================
|
||||||
|
|
||||||
Foo
|
Most (but not all) RPM spec files will have a `Release` tag that contains
|
||||||
|
the following:
|
||||||
|
|
||||||
|
Release: %{?repo}N%{?dist}
|
||||||
|
|
||||||
|
|
||||||
|
where `N` is *usually* either a positive integer or is of the form
|
||||||
|
`0.rcM` or `0.devM` where `M` is an integer.
|
||||||
|
|
||||||
|
The idea behind this added complexity to the `Release` tag is so that
|
||||||
|
different repositories can exist that have duplicate packages sometimes
|
||||||
|
even built from the same RPM spec file but with different capabilities.
|
||||||
|
|
||||||
|
These repositories can then have a hierarchal `repo` macro so that as
|
||||||
|
long as the `Version` is the same, the repository with the greater
|
||||||
|
`repo` tag will always resolve as the newer package to RPM.
|
||||||
|
|
||||||
|
This can help avoid things like GNU Emacs linked against X11 from being
|
||||||
|
replaced by a GNU Emacs package that is not linked against X11 just
|
||||||
|
because a “lower-level” package repository rebuilt GNU Emacs with a
|
||||||
|
larger `N` than the “higher-level” package repository uses.
|
||||||
|
Loading…
Reference in New Issue
Block a user