Automic VaultAutomic Vault

brew

tradcpp mit Homebrew, MacPorts, Nix installieren

Prüfe Installationswege, Executables, Metadaten und Sicherheitshinweise für tradcpp in AI-Agent-Workflows.

Installation

Weitere Installationsbefehle

macOS

Homebrewverifiziert · 100%
brew install tradcpp

local Homebrew formula metadata

MacPortsverifiziert · 94%
sudo port install tradcpp

MacPorts ports tree · devel/tradcpp/Portfile · Quelle: api.github.com

Linux

Nixverifiziert · 92%
nix profile install nixpkgs#tradcpp

nixpkgs package indexes · pkgs/by-name/tr/tradcpp/package.nix · Quelle: api.github.com

Überblick

Paketzusammenfassung

K&R-style C preprocessor

Verlauf

Projektgeschichte und Nutzung

tradcpp is a small traditional, K&R-style C preprocessor maintained from David Holland's NetBSD pages. Its history is tied less to compiling C and more to preserving old build techniques that used cpp as a general text preprocessor.

Projektgeschichte

The official tradcpp page says the tool was written for historical uses of the C preprocessor on non-C input, because modern compiler-bundled preprocessors increasingly do not provide a traditional mode or preserve the behavior old build systems expect. The project deliberately keeps a narrow scope and does not try to become a full modern C89/C99/C11 preprocessor.

A distinctive implementation goal is whitespace preservation. The author calls out makefiles, old Emacs build logic, and imake as examples where rearranging whitespace can break legacy systems. tradcpp also includes a trace mode for diagnosing complex preprocessor use; the page says it was written to investigate an imake problem on Solaris.

Adoptionsgeschichte

The most explicit adoption history is in pkgsrc: the official page says pkgsrc, the NetBSD package system, has used tradcpp for these purposes since 2013. That makes tradcpp a package-system support tool rather than a broad end-user application.

Wie es verwendet wird

In package-manager culture, tradcpp is used when a build recipe needs a traditional cpp that preserves old preprocessing behavior for files such as makefiles. Users are explicitly steered away from using it for normal modern C code.

Warum Paket-Nerds sich dafür interessieren

tradcpp matters to package nerds because it is infrastructure for keeping old source packages buildable. It represents the unglamorous compatibility layer a portability framework like pkgsrc sometimes needs when upstream build systems rely on historical Unix behavior.

Zeitleiste

  • 2013: pkgsrc begins using tradcpp for legacy preprocessing use cases.
  • Current official release: tradcpp 0.5.3 is listed on the NetBSD-hosted project page.

Related projects

  • pkgsrc uses tradcpp for package builds with legacy preprocessing needs.
  • imake and old Emacs build systems are named by the author as examples of the historical cpp usage tradcpp was designed to support.

Sicherheitslage

Risikostufe: grün

narrow executable package without higher-risk signals.

Risikoklassifikator

grün Risiko · niedrig Konfidenz · appliance

Warum

  • narrow executable package without higher-risk signals

Signale

  • metadata:no-higher-risk-signals

Installationsverhalten

  • In den Formelmetadaten ist kein Homebrew-Post-install-Hook erfasst.
  • Homebrew-Bottle-Metadaten sind für 12 Plattformziele verfügbar.
  • Build-Metadaten listen 1 Build-Abhängigkeiten.

Empfohlene Prüfung

Prüfe vor unbeaufsichtigter Agent-Nutzung, ob das Tool Klartext-Credentials liest, Remote-Zustand schreibt, Artefakte veröffentlicht oder Plugins ausführt.

Executables

Installierte Executables

BefehlArtSichtbarkeitHinweis
tradcppcliglobales Executable

Aktualität

Version und Aktualität

Diese Signale trennen das Alter der Seitengenerierung, Aktivität des Paketmanagers und Upstream-Release-Vergleich. Versionsrückstand wird nur gemeldet, wenn eine Evidenz-URL und vergleichbare Versionen vorhanden sind.

Seite generiert2026-07-08
Manager-Version0.5.3
Manager aktualisiert
lokale DatenOK
Upstreamnot checked
neueste erkannte Versionnicht erkannt

https://www.netbsd.org/~dholland/tradcpp/

Installationsmetadaten

Paketmetadaten

Paketschlüsselbrew:tradcpp
Version0.5.3
PaketmanagerHomebrew
Paketmanager-Seitehttps://formulae.brew.sh/formula/tradcpp
Homepagehttps://www.netbsd.org/~dholland/tradcpp/
Repositoryhttps://www.netbsd.org/~dholland/hg/tradcpp
Upstream-Dokumentationhttps://www.netbsd.org/~dholland/tradcpp
LizenzBSD-2-Clause
Quellarchivhttps://cdn.netbsd.org/pub/NetBSD/misc/dholland/tradcpp-0.5.3.tar.gz
Build-Abhängigkeitenbmake
Bottleverfügbar (auf arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, monterey, sonoma, ventura, x86_64_linux)
Homebrew post-installnicht definiert
Dienstkeiner deklariert

Registry-Fakten

Details aus der Quelldatenbank

Source DatabaseHomebrew formula API
Taphomebrew/core
Full Nametradcpp
Version Scheme0
Revision0
Bottle Stable Root URLhttps://ghcr.io/v2/homebrew/core
Deprecatedno
Disabledno
Keg Onlyno
URL Keys
  • stable

Source-Datenbank-Treffer

Andere Paketmanager-Einträge

Treffer stammen aus externen Paketmanager-Indizes und bleiben von lokalen Automic-Vault-Paketlinks getrennt.

Nix95%

tradcpp

nix profile install nixpkgs#tradcpp
  • normalized package name match
  • Abgeglichen nach: Tradcpp
nixpkgs package indexes · api.github.com · nixpkgs package indexes: pkgs/by-name/tr/tradcpp/package.nix from https://api.github.com/repos/NixOS/nixpkgs/git/trees/master?recursive=1
MacPorts95%

tradcpp

sudo port install tradcpp
  • normalized package name match
  • Abgeglichen nach: Tradcpp
MacPorts ports tree · api.github.com · MacPorts ports tree: devel/tradcpp/Portfile from https://api.github.com/repos/macports/macports-ports/git/trees/master?recursive=1

Quellspur

Aus Repository-Daten generiert

Diese Seite wird von av-web aus dem privaten Paket-SQLite-Artefakt bereitgestellt, das scripts/generate-pkg-sqlite.py erstellt.

Verwendete Quellen

  • Geiger risk classifier
  • Nucleus package database
  • av.db category and tag curation
  • cross-ecosystem install command graph
  • curated package history
  • external package-manager database matches
  • package relationship graph
  • package version freshness
  • package-page enrichment