summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndrew Ammerlaan <andrewammerlaan@gentoo.org>2021-05-22 22:37:36 +0200
committerAndrew Ammerlaan <andrewammerlaan@gentoo.org>2021-05-22 22:55:44 +0200
commit9358fd314ef7345110d1f4d8192365736bab23bc (patch)
tree4cff94704bc43967465bb71ad2b43acfd2eeae6d /dev-python/bracex
parentdev-python/backrefs: add <stabilize-allarches/> (diff)
downloadgentoo-9358fd314ef7345110d1f4d8192365736bab23bc.tar.gz
gentoo-9358fd314ef7345110d1f4d8192365736bab23bc.tar.bz2
gentoo-9358fd314ef7345110d1f4d8192365736bab23bc.zip
dev-python/bracex: add <stabilize-allarches/>
Package-Manager: Portage-3.0.18, Repoman-3.0.3 Signed-off-by: Andrew Ammerlaan <andrewammerlaan@gentoo.org>
Diffstat (limited to 'dev-python/bracex')
-rw-r--r--dev-python/bracex/metadata.xml1
1 files changed, 1 insertions, 0 deletions
diff --git a/dev-python/bracex/metadata.xml b/dev-python/bracex/metadata.xml
index 8badec61ee20..106da756d0bb 100644
--- a/dev-python/bracex/metadata.xml
+++ b/dev-python/bracex/metadata.xml
@@ -22,4 +22,5 @@
Bracex actually follows pretty closely to how Bash processes braces. It is not a 1:1 implementation of how Bash handles braces, but generally, it follows very closely. Almost all of the test cases are run through Bash first, then our implementation is compared against the results Bash gives. There are a few cases where we have purposely deviated. For instance, we are not handling Bash's command line inputs, so we are not giving special meaning to back ticks and quotes at this time.
</longdescription>
+ <stabilize-allarches/>
</pkgmetadata>