Linux workstation

Upstream software project

libtext-brew-perl

An implementation of the Brew edit distance

About libtext-brew-perl

An implementation of the Brew edit distance

This project links 5 native package records across 5 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Project pictures and package coverage

Debian 12 (Bookworm): 1 package records; Debian 13 (Trixie): 1 package records; Fedora 43: 1 package records; Fedora 44: 1 package records; openSUSE Tumbleweed: 1 package records. Catalog coverage diagram, not an application screenshot.libtext-brew-perl: recorded package coverageDebian 12 (Bookworm)1 recordsDebian 13 (Trixie)1 recordsFedora 431 recordsFedora 441 recordsopenSUSE Tumbleweed1 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
libtext-brew-perl
Publisher
Not authoritatively mapped
Native package records
5
Operating systems
debian-12, debian-13, fedora-43, fedora-44, opensuse-tumbleweed
License expression
Artistic-1.0 OR GPL-1.0-or-later
Metadata completeness
100/100 (not a software quality rating)
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

This module implements the Brew edit distance that is very close to the dynamic programming technique used for the Wagner-Fischer (and so for the Levenshtein) edit distance. Please look at the module references below. For more information about the Brew edit distance see: <http://ling.ohio-state.edu/~cbrew/795M/string-distance.html> The difference here is that you have separated costs for the DELetion and INSertion operations (but with the default to 1 for both, you obtain the Levenshtein edit distance). But the most interesting feature is that you can obtain the description of the edits needed to transform the first string into the second one (not vice versa: here DELetions are separated from INSertions). The difference from the original algorithm by Chris Brew is that I have added the SUBST operation, making it different from MATCH operation. The symbols used here are: INITIAL that is the INITIAL operation (i.e. NO operation) MATCH that is the MATCH operation (0 is the default cost) SUBST that is the SUBSTitution operation (1 is the default cost) DEL that is the DELetion operation (1 is the default cost) INS that is the INSertion operation (1 is the default cost) and you can change the default costs (see below). You can make INS and DEL the same operation in a simple way: 1) give both the same cost 2) change the output string DEL to INS/DEL (o whatever) 3) change the output string INS to INS/DEL (o whatever)

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Debian 12 (Bookworm)

  1. libtext-brew-perl

    Debian 12 (Bookworm) / perl

    0.02-3

    perl implementation of Brew edit distance

    allbookworm

Debian 13 (Trixie)

  1. libtext-brew-perl

    Debian 13 (Trixie) / perl

    0.02-3

    perl implementation of Brew edit distance

    alltrixie

Fedora 43

  1. perl-Text-Brew

    Fedora 43 / Unspecified / source perl-Text-Brew

    0.02-32.fc43

    Implementation of the Brew edit distance

    noarch43

Fedora 44

  1. perl-Text-Brew

    Fedora 44 / Unspecified / source perl-Text-Brew

    0.02-33.fc44

    Implementation of the Brew edit distance

    noarch44

openSUSE Tumbleweed

  1. perl-Text-Brew

    openSUSE Tumbleweed / Unspecified / source perl-Text-Brew

    0.20.0-1.4

    An implementation of the Brew edit distance

    noarchtumbleweed

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.