diff options
author | Panu Matilainen <pmatilai@redhat.com> | 2010-12-13 12:03:18 +0200 |
---|---|---|
committer | Panu Matilainen <pmatilai@redhat.com> | 2010-12-13 12:26:06 +0200 |
commit | 5c43095e1d78b3befe93c746fd182746c3b96c92 (patch) | |
tree | c57347a08501be44320ce49c36a774ff6c647b8b /tests | |
parent | 185de185262b2772fa692efc69633f41afc5832a (diff) | |
download | rpm-5c43095e1d78b3befe93c746fd182746c3b96c92.tar.gz rpm-5c43095e1d78b3befe93c746fd182746c3b96c92.tar.bz2 rpm-5c43095e1d78b3befe93c746fd182746c3b96c92.zip |
Implement transaction ordering hinting
- Add support for new "OrderWithRequires: foo" spec syntax
which has "if and only if foo is present in transaction, order
the transaction as if this package required foo" semantics.
While it looks, and in some ways is, a soft dependency, this
is not the same as recommends/suggests etc: those have unknown
depsolver policy dependent semantics attached to them, whereas
ordering hints have a clear definition and is only relevant for rpm
itself, depsolvers should not even look at the data.
- This allows packages to express correct ordering for optional
functionality, such as
%post
if [ -x %{_bindir}/register-component ]; then
%{_bindir}/register-component %{name}
fi
If the package containing %{_bindir}/register-component is included
in the same transaction, it makes sense to have it installed before the
package(s) that use it. But as it is fully optional, Requires would
not be appropriate. Using OrderWithRequires allows this to be expressed
without dragging in extraneous dependencies for optional functionality.
Diffstat (limited to 'tests')
-rw-r--r-- | tests/rpmgeneral.at | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/tests/rpmgeneral.at b/tests/rpmgeneral.at index 9c64bb464..cd901180a 100644 --- a/tests/rpmgeneral.at +++ b/tests/rpmgeneral.at @@ -163,6 +163,9 @@ OBSOLETES OBSOLETEVERSION OLDFILENAMES OPTFLAGS +ORDERFLAGS +ORDERNAME +ORDERVERSION ORIGBASENAMES ORIGDIRINDEXES ORIGDIRNAMES |