commit:     a56ac7179b9a1cd86634f1d71c2a3d419ee2ddad
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Dec 23 17:44:03 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Dec 23 17:44:03 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a56ac717

dev-libs/libslz: fix metadata.xml typo

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-libs/libslz/metadata.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-libs/libslz/metadata.xml b/dev-libs/libslz/metadata.xml
index 00eae7153ae7..a87f2b797b7a 100644
--- a/dev-libs/libslz/metadata.xml
+++ b/dev-libs/libslz/metadata.xml
@@ -12,7 +12,7 @@
        <longdescription>
 SLZ is a fast and memory-less stream compressor which produces an output that 
can be decompressed with zlib or gzip. It does not implement decompression at 
all, zlib is perfectly fine for this.
 
-The purpose is to use SLZ in situations where a zlib-compatible stream is 
needed and zlib's resource usage would be too high while the compression ratio 
is not critical. The typical use case is in HTTP servers and gateways which 
have to compress many streams in parallel with little CPU resources to assign 
to this task, and without having to thottle the compression ratio due to the 
memory usage. In such an environment, the server's memory usage can easily be 
divided by 10 and the CPU usage by 3
+The purpose is to use SLZ in situations where a zlib-compatible stream is 
needed and zlib's resource usage would be too high while the compression ratio 
is not critical. The typical use case is in HTTP servers and gateways which 
have to compress many streams in parallel with little CPU resources to assign 
to this task, and without having to throttle the compression ratio due to the 
memory usage. In such an environment, the server's memory usage can easily be 
divided by 10 and the CPU usage by 3
        </longdescription>
        <use>
                <flag name="tools">Install additional tools (zenc, zdec)</flag>

Reply via email to