ref-manual: Added versioning to some R* variables
Fixes [YOCTO #4987] Added some versioning operators to the RCONFLICTS, RREPLACES, and RRECOMMENDS variables. I am using the same base text to get this information across. Because it is a referenced glossary, the duplication is acceptable. (From yocto-docs rev: 47613f962c945e06710ba2e14e0eb5f1f11d0336) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
parent
6084246825
commit
d3bf6bd677
|
@ -4078,17 +4078,46 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
|||
|
||||
<glossentry id='var-RCONFLICTS'><glossterm>RCONFLICTS</glossterm>
|
||||
<glossdef>
|
||||
<para>The list of packages that conflict with another package.
|
||||
Note that the package will not be installed if the conflicting packages are not
|
||||
first removed.</para>
|
||||
<para>
|
||||
Like all package-controlling variables, you must always use them in
|
||||
conjunction with a package name override.
|
||||
The list of packages that conflict with packages.
|
||||
Note that packages will not be installed if conflicting
|
||||
packages are not first removed.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
Like all package-controlling variables, you must always use
|
||||
them in conjunction with a package name override.
|
||||
Here is an example:
|
||||
<literallayout class='monospaced'>
|
||||
RCONFLICTS_${PN} = "another-conflicting-package-name"
|
||||
</literallayout>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
BitBake, which the OpenEmbedded build system uses, supports
|
||||
specifying versioned dependencies.
|
||||
Although the syntax varies depending on the packaging
|
||||
format, BitBake hides these differences from you.
|
||||
Here is the general syntax to specify versions with
|
||||
the <filename>RCONFLICTS</filename> variable:
|
||||
<literallayout class='monospaced'>
|
||||
RCONFLICTS_${PN} = "<package> (<operator> <version>)"
|
||||
</literallayout>
|
||||
For <filename>operator</filename>, you can specify the
|
||||
following:
|
||||
<literallayout class='monospaced'>
|
||||
=
|
||||
<
|
||||
>
|
||||
<=
|
||||
>=
|
||||
</literallayout>
|
||||
For example, the following sets up a dependency on version
|
||||
1.2 or greater of the package <filename>foo</filename>:
|
||||
<literallayout class='monospaced'>
|
||||
RCONFLICTS_${PN} = "foo (>= 1.2)"
|
||||
</literallayout>
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
@ -4344,6 +4373,32 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
|||
namespace before any renaming of the output package by
|
||||
classes such as <filename>debian.bbclass</filename>.
|
||||
</para>
|
||||
|
||||
<para>
|
||||
BitBake, which the OpenEmbedded build system uses, supports
|
||||
specifying versioned recommends.
|
||||
Although the syntax varies depending on the packaging
|
||||
format, BitBake hides these differences from you.
|
||||
Here is the general syntax to specify versions with
|
||||
the <filename>RRECOMMENDS</filename> variable:
|
||||
<literallayout class='monospaced'>
|
||||
RRECOMMENDS_${PN} = "<package> (<operator> <version>)"
|
||||
</literallayout>
|
||||
For <filename>operator</filename>, you can specify the
|
||||
following:
|
||||
<literallayout class='monospaced'>
|
||||
=
|
||||
<
|
||||
>
|
||||
<=
|
||||
>=
|
||||
</literallayout>
|
||||
For example, the following sets up a recommend on version
|
||||
1.2 or greater of the package <filename>foo</filename>:
|
||||
<literallayout class='monospaced'>
|
||||
RRECOMMENDS_${PN} = "foo (>= 1.2)"
|
||||
</literallayout>
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
@ -4368,6 +4423,33 @@ recipes-graphics/xorg-font/font-alias_1.0.3.bb:PR = "${INC_PR}.3"
|
|||
RREPLACES_${PN} = "other-package-being-replaced"
|
||||
</literallayout>
|
||||
</para>
|
||||
|
||||
<para>
|
||||
BitBake, which the OpenEmbedded build system uses, supports
|
||||
specifying versioned replacements.
|
||||
Although the syntax varies depending on the packaging
|
||||
format, BitBake hides these differences from you.
|
||||
Here is the general syntax to specify versions with
|
||||
the <filename>RREPLACES</filename> variable:
|
||||
<literallayout class='monospaced'>
|
||||
RREPLACES_${PN} = "<package> (<operator> <version>)"
|
||||
</literallayout>
|
||||
For <filename>operator</filename>, you can specify the
|
||||
following:
|
||||
<literallayout class='monospaced'>
|
||||
=
|
||||
<
|
||||
>
|
||||
<=
|
||||
>=
|
||||
</literallayout>
|
||||
For example, the following sets up a replacement using
|
||||
version 1.2 or greater of the package
|
||||
<filename>foo</filename>:
|
||||
<literallayout class='monospaced'>
|
||||
RREPLACES_${PN} = "foo (>= 1.2)"
|
||||
</literallayout>
|
||||
</para>
|
||||
</glossdef>
|
||||
</glossentry>
|
||||
|
||||
|
|
Loading…
Reference in New Issue