aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorAvatar Ciaran McCreesh <ciaran.mccreesh@googlemail.com> 2011-04-04 14:54:38 +0100
committerAvatar Ciaran McCreesh <ciaran.mccreesh@googlemail.com> 2011-04-04 14:54:38 +0100
commit5c950263e9ea902e86030b5fd3a8c6b0760e7539 (patch)
treeeff1ba8b39ba44dc332f470c9717a896813b7b7c /doc
parentb3d3ba6393d47447c9ee5fe444683d2409b3cd2d (diff)
downloadpaludis-5c950263e9ea902e86030b5fd3a8c6b0760e7539.tar.gz
paludis-5c950263e9ea902e86030b5fd3a8c6b0760e7539.tar.xz
[.key~value] operator
Diffstat (limited to 'doc')
-rw-r--r--doc/configuration/specs.html.part8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/configuration/specs.html.part b/doc/configuration/specs.html.part
index ad3758eca..40833f3de 100644
--- a/doc/configuration/specs.html.part
+++ b/doc/configuration/specs.html.part
@@ -46,10 +46,10 @@ the following order:</p>
<li><code>[.key=value]</code>: Match only if the specified metadata key has a particular exact value. Only works for
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>
+ a match occurs if any member of the set or sequence is equal to the value. If <code>&gt;</code> is used,
+ for numeric values a greater-than comparison is used; it does not match for other types of values. If <code>~</code>
+ is used, a substring match is performed. 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