Bug 357393 – dev-libs/tre: agrep filename clash with app-misc/glimpse and app-text/agrep

• Product: Gentoo Linux
• Status: RESOLVED DUPLICATE

[Description Martin Mokrejš 2011-03-04 16:51:08 UTC]

I want to install tre library with its python interface. The agrep is a bonus from the bundle. I see the file collision is resolved currently by packages blocking each other. I propose renaming agrep from tre package to agrep.tre.

There is still open bug #296813 and per comments in the ebuild, I am showing below the differences between the two agrep utilities. Somebody else install the app-text/agrep.


agrep from tre says:

Usage: agrep [OPTION]... PATTERN [FILE]...
Searches for approximate matches of PATTERN in each FILE or standard input.
Example: `agrep -2 optimize foo.txt' outputs all lines in file `foo.txt' that
match "optimize" within two errors.  E.g. lines which contain "optimise",
"optmise", and "opitmize" all match.

Regexp selection and interpretation:
  -e, --regexp=PATTERN      use PATTERN as a regular expression
  -i, --ignore-case         ignore case distinctions
  -k, --literal             PATTERN is a literal string
  -w, --word-regexp         force PATTERN to match only whole words

Approximate matching settings:
  -D, --delete-cost=NUM     set cost of missing characters
  -I, --insert-cost=NUM     set cost of extra characters
  -S, --substitute-cost=NUM set cost of wrong characters
  -E, --max-errors=NUM      select records that have at most NUM errors
  -#                        select records that have at most # errors (# is a
                            digit between 0 and 9)

Miscellaneous:
  -d, --delimiter=PATTERN   set the record delimiter regular expression
  -v, --invert-match        select non-matching records
  -V, --version             print version information and exit
  -y, --nothing             does nothing (for compatibility with the non-free
                            agrep program)
      --help                display this help and exit

Output control:
  -B, --best-match          only output records with least errors
  -c, --count               only print a count of matching records per FILE
  -h, --no-filename         suppress the prefixing filename on output
  -H, --with-filename       print the filename for each match
  -l, --files-with-matches  only print FILE names containing matches
  -M, --delimiter-after     print record delimiter after record if -d is used
  -n, --record-number       print record number with output
      --line-number         same as -n
  -q, --quiet, --silent     suppress all normal output
  -s, --show-cost           print match cost with output
      --colour, --color     use markers to distinguish the matching strings
      --show-position       prefix each output record with start and end
                            position of the first match within the record

With no FILE, or when FILE is -, reads standard input.  If less than two
FILEs are given, -h is assumed.  Exit status is 0 if a match is found, 1 for
no match, and 2 if there were errors.  If -E or -# is not specified, only
exact matches are selected.

PATTERN is a POSIX extended regular expression (ERE) with the TRE extensions.
See tre(7) for a complete description.

Report bugs to: [e-mail].



In contrast, agrep from glimpse says:
usage: agrep [-@#abcdehiklnoprstvwxyBDGIMSV] [-f patternfile] [-H dir] pattern [files]

summary of frequently used options:
(For a more detailed listing see 'man agrep'.)
-#: find matches with at most # errors
-c: output the number of matched records
-d: define record delimiter
-h: do not output file names
-i: case-insensitive search, e.g., 'a' = 'A'
-l: output the names of files that contain a match
-n: output record prefixed by record number
-v: output those records that have no matches
-w: pattern has to match as a word, e.g., 'win' will not match 'wind'
-B: best match mode. find the closest matches to the pattern
-G: output the files that contain a match
-H 'dir': the cast-dictionary is located in directory 'dir'

[Comment 1 Justin Lecher (RETIRED) 2011-03-04 18:12:10 UTC]

*** This bug has been marked as a duplicate of bug 288618 ***