pkg.sopackage field notes

brew / rang 5197

Installer bsdiff avec Homebrew

Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de bsdiff pour les workflows d'agents IA.

installation

Commandes d'installation supplémentaires

macOS

Homebrewvérifié · 100%
brew install bsdiff

provider-native install command

aperçu

Résumé du paquet

Generate and apply patches to binary files

Commandes et alias

  • bsdiff

historique

Historique du projet et usages

bsdiff and bspatch are Colin Percival's binary diff and patch tools, best known for producing small patches for executable files. The package is tiny, old, and still important because binary delta updates remain a core packaging and updater trick.

Historique du projet

The official page describes bsdiff and bspatch as tools for building and applying binary patches. It explains that they use suffix sorting, specifically Larsson and Sadakane's qsufsort, and exploit the way executable files change to make much smaller patches than contemporary binary patch tools.

The same page says the programs were originally named `bdiff` and `bpatch`, but were renamed because many other programs used those names. It published version 4.3 as a tarball and identifies the BSDiff 4 algorithm with Percival's 2003 paper, `Naive differences of executable code`.

Historique d'adoption

By the time version 4.2 was described on the official page, bsdiff was already in the FreeBSD, NetBSD, and OpenBSD ports trees, DarwinPorts, Gentoo, and as a Python extension module. The provided package facts show wider modern packaging across Homebrew, Debian, Fedora/dnf, MacPorts, Nix, Ubuntu, and openSUSE/zypper.

bsdiff also influenced the packaging and update world indirectly: binary delta algorithms of this style are natural fits for software update systems, where shaving patch size saves bandwidth and time.

Modes d'utilisation

`bsdiff` compares an old file and a new file to produce a compact patch; `bspatch` applies that patch to reconstruct the new file. The package is most useful for compiled binaries and other files where line-oriented text diffs are ineffective.

The official page documents its resource profile: bsdiff is memory-hungry and runs in O((n+m) log n), while bspatch runs in O(n+m). That tradeoff is acceptable for many release pipelines because patch creation happens once, while patch application may happen many times.

Pourquoi les passionnés de paquets s'y intéressent

bsdiff is package-nerd famous because it is a small command with an outsized effect on binary distribution. It gives maintainers a simple way to ship deltas instead of whole files, and its paper made the algorithm understandable enough to reimplement and adapt.

It is also a classic example of a package whose upstream is not a modern forge repository. Package managers preserve the tool through tarballs, patches, and downstream maintenance even without a canonical GitHub-style source-control home.

Chronologie

  • 2003: Colin Percival describes the BSDiff 4 algorithm in `Naive differences of executable code`.
  • 2000s: Version 4.2 is available in FreeBSD, NetBSD, OpenBSD ports, DarwinPorts, Gentoo, and as a Python extension.
  • 2005: Version 4.3 is published on the official daemonology.net bsdiff page.
  • 2026: Provided package facts show bsdiff available across Homebrew, Debian, Fedora/dnf, MacPorts, Nix, Ubuntu, and openSUSE/zypper.

Related projects

  • bspatch is the companion patch-application utility shipped with bsdiff.
  • xdelta is the comparison tool named by the official page for binary delta compression.
  • RTPatch is the commercial binary patch tool named by the official page as another comparison point.
  • FreeBSD Update is historically associated with Colin Percival's binary-update work and the wider bsdiff ecosystem.

posture de sécurité

Niveau de risque : vert

narrow executable package without higher-risk signals.

Classificateur de risque

risque vert · confiance faible · appliance

Pourquoi

  • narrow executable package without higher-risk signals

Signaux

  • metadata:no-higher-risk-signals

Comportement d'installation

  • Aucune métadonnée de bottle Homebrew n’a été enregistrée.

Revue recommandée

Avant une utilisation sans surveillance par un agent, vérifiez si l'outil lit des identifiants en clair, écrit un état distant, publie des artefacts ou lance des plugins.

exécutables

Exécutables installés

CommandeTypeExpositionNote
bsdiffexécutableexécutable indexéDécouvert depuis l'index local des exécutables.

fraîcheur

Version et fraîcheur

Ces signaux séparent l'âge de génération de la page, l'activité du gestionnaire de paquets et la comparaison avec les versions amont. Un retard de version n'est signalé que lorsqu'une URL de preuve et des versions comparables sont présentes.

page générée2026-08-03
version du gestionnaire4.3
gestionnaire mis à jour
données localesinconnu
amontnon disponible
dernière version détectéenon détecté
  • OKAucun avertissement de fraîcheur n'a été généré.

métadonnées d'installation

Métadonnées du paquet

Clé du paquetbrew:bsdiff
Version4.3
Gestionnaire de paquetsHomebrew
Page d'accueilhttps://www.daemonology.net/bsdiff/
Bouteillenon enregistré
Serviceaucun déclaré

piste source

Généré depuis les données du dépôt

Cette page est servie par av-web depuis l'artéfact SQLite privé des paquets généré par scripts/generate-pkg-sqlite.py.

Sources utilisées

  • Geiger risk classifier
  • Nucleus package database
  • curated package history
  • pkgdb category and tag curation