aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorAvatar Benedikt Morbach <moben@exherbo.org> 2013-03-05 02:29:11 +0100
committerAvatar Ciaran McCreesh <ciaran.mccreesh@googlemail.com> 2013-03-08 12:53:36 +0000
commit26c5ed12c5067a5d83437197379f65dfc4a06fcc (patch)
treee75ddf436c24efe12cdd08291056a12b5cb0da5a /doc
parentcab157fad7e41ec29d3989d3aebaefbf202de6bd (diff)
downloadpaludis-26c5ed12c5067a5d83437197379f65dfc4a06fcc.tar.gz
paludis-26c5ed12c5067a5d83437197379f65dfc4a06fcc.tar.xz
UserKeyRequirement: allow matching metadata for inequality
only for simple values. Note that this changes behaviour in the following way: Previously, any of '><=' would be treated as '='. Now, only '=' and '!' are respected and '<' and '>' always return false. The only simple value key which still takes all operators is <long> because there it makes sense.
Diffstat (limited to 'doc')
-rw-r--r--doc/configuration/specs.html.part6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/configuration/specs.html.part b/doc/configuration/specs.html.part
index ad3758eca..05372dcc6 100644
--- a/doc/configuration/specs.html.part
+++ b/doc/configuration/specs.html.part
@@ -47,9 +47,9 @@ the following order:</p>
simple values, sets and sequences, not spec trees and other complex compound keys. If <code>&lt;</code> is used in
place of <code>=</code>, for numeric values a less-than comparison is used, and for sets, sequences and spec trees,
a match occurs if any member of the set or sequence is equal to the value. Similarly if <code>&gt;</code> is used,
- for numeric values a greater-than comparison is used; it does not match for other types of values. As above, the key
- may be a raw name or a dollar-prefixed role name, and may be prefixed with <code>::</code> for checking repository
- metadata.</li>
+ for numeric values a greater-than comparison is used; it does not match for other types of values. If <code>!=</code>
+ is used for simple values, a not-equal comparison is used. As above, the key may be a raw name or a dollar-prefixed
+ role name, and may be prefixed with <code>::</code> for checking repository metadata.</li>
</ul>
<p>Repository requirements are in the form <code>to</code>, <code>from-&gt;</code> or <code>::from-&gt;to</code>. The