~/f/ripgrep/RPMS.2017 ~/f/ripgrep
~/f/ripgrep
RPMS.2017/ripgrep-11.0.2-0.0.x86_64.rpm RPMS/ripgrep-11.0.2-0.0.x86_64.rpm differ: byte 225, line 1
Comparing ripgrep-11.0.2-0.0.x86_64.rpm to ripgrep-11.0.2-0.0.x86_64.rpm
comparing the rpm tags of ripgrep
--- /tmp/tmp.IohDAK9Lu3/tmp.Iwy6w0eZks	2019-12-01 18:51:58.410132145 +0000
+++ /tmp/tmp.IohDAK9Lu3/tmp.qlEneYsxYK	2019-12-01 18:51:58.414132176 +0000
@@ -93,7 +93,7 @@
 /usr/share/licenses/ripgrep  0
 /usr/share/licenses/ripgrep/LICENSE-MIT 0f96a83840e146e43c0ec96a22ec1f392e0680e6c1226e6f3ba87e0740af850f 128
 /usr/share/licenses/ripgrep/UNLICENSE 7e12e5df4bae12cb21581ba157ced20e1986a0508dd10d0e8a4ab9a4cf94e85c 128
-/usr/share/man/man1/rg.1.gz fcc72d7fbbdd59aa52486e4e279b70b244266aa08805016df6a5914cc72a9c9e 2
+/usr/share/man/man1/rg.1.gz 3f4fdb9852b32f966ef50bb9c0bc454effd0c2865d8c7eb91b0bf3e922379c7d 2
 
 
 ___QF_CHECKSUM___
comparing rpmtags
comparing RELEASE
comparing PROVIDES
comparing scripts
comparing filelist
comparing file checksum
creating rename script
RPM file checksum differs.
Extracting packages
/usr/share/man/man1/rg.1 differs (troff or preprocessor input, ASCII text, with very long lines)
--- old//usr/share/man/man1/rg.1	2019-12-01 18:51:59.122137558 +0000
+++ new//usr/share/man/man1/rg.1	2019-12-01 18:51:59.158137832 +0000
@@ -1368,7 +1368,7 @@
 ripgrep may use a large amount of memory depending on a few factors\&. Firstly, if ripgrep uses parallelism for search (the default), then the entire output for each individual file is buffered into memory in order to prevent interleaving matches in the output\&. To avoid this, you can disable parallelism with the \fB\-j1\fR flag\&. Secondly, ripgrep always needs to have at least a single line in memory in order to execute a search\&. A file with a very long line can thus cause ripgrep to use a lot of memory\&. Generally, this only occurs when searching binary data with the \fB\-a\fR flag enabled\&. (When the \fB\-a\fR flag isn\(cqt enabled, ripgrep will replace all NUL bytes with line terminators, which typically prevents exorbitant memory usage\&.) Thirdly, when ripgrep searches a large file using a memory map, the process will report its resident memory usage as the size of the file\&. However, this does not mean ripgrep actually needed to use that much memory; the operating system will generally handle this for you\&.
 .SH "VERSION"
 .sp
-11\&.0\&.2 \-SIMD \-AVX (compiled) +SIMDrun \-AVXrun2 (runtime)
+11\&.0\&.2 \-SIMD \-AVX (compiled) \-SIMDrun3 \-AVXrun2 (runtime)
 .SH "HOMEPAGE"
 .sp
 https://github\&.com/BurntSushi/ripgrep
overalldiffered=1 (not bit-by-bit identical)
overall=1