deja-gnu mit Homebrew, apk, apt, dnf, MacPorts, Nix, pacman, zypper installieren

Projektlinks

• Homepage
• Repository
• Upstream-Dokumentation
• Paketmanager-Seite

Befehle und Aliase

• dejagnu
• runtest

Projektgeschichte

DejaGnu became a GNU package to solve a very GNU problem: testing compilers, debuggers, binutils, and other portable development tools across many hosts and targets. Its Savannah project page identifies the official GNU project and source repository, while the GNU manual documents the runtest harness, board files, site configuration, and per-user startup file used by the framework.

The GNU FTP archive shows DejaGnu releases dating back to the 1.3 series in 1996, followed by long-lived 1.4, 1.5, and 1.6 release lines. That release pattern mirrors its role as infrastructure: the tool changes slowly, but it remains important wherever old and new toolchains need repeatable test results.

Adoptionsgeschichte

DejaGnu's adoption is tied to the GNU toolchain rather than to application development fashion. Projects that need to run the same tests against native binaries, cross targets, simulators, or remote boards use DejaGnu because its abstraction is old, boring, and understood by compiler and embedded developers.

The package is widely shipped by Unix-like package managers because it is a build and test dependency for other low-level software. Homebrew packages it as deja-gnu, while GNU distributes canonical source tarballs through ftp.gnu.org.

Wie es verwendet wird

Users normally invoke the runtest command from a package testsuite. Site-wide and user-specific configuration can tune board definitions, tool paths, and target behavior through site.exp and ~/.dejagnurc.

DejaGnu matters most when tests must be portable across machines rather than just run locally. The same test description can talk to a native program, a remote target, or a simulator through Expect-driven interactions.

Warum Paket-Nerds sich dafür interessieren

For package maintainers, DejaGnu is one of the classic pieces of GNU release machinery: not glamorous, but deeply embedded in the way compilers and binary tools prove they still work.

Its presence in dependency graphs often signals that a formula or distribution package is running upstream's real tests instead of a smoke test. That makes it an important clue when auditing build quality for toolchain packages.

Zeitleiste

• 1996: DejaGnu 1.3 appears in the GNU FTP archive.
• 2001: The 1.4 release line is distributed through GNU FTP.
• 2011: DejaGnu 1.5 is released after a long 1.4 maintenance period.
• 2016: DejaGnu 1.6 is released.
• 2021: DejaGnu 1.6.3 is published in the GNU FTP archive.

Related projects

• Expect and Tcl provide the interaction layer DejaGnu uses to drive programs under test.
• GCC, GDB, and Binutils are representative GNU toolchain projects whose testing culture overlaps with DejaGnu.
• Autotest and Automake are adjacent GNU testing and build tools, but DejaGnu specializes in target-oriented test execution.

Quellen

• https://savannah.gnu.org/projects/dejagnu
• https://git.savannah.gnu.org/cgit/dejagnu.git
• https://ftp.gnu.org/gnu/dejagnu/
• https://www.gnu.org/software/dejagnu/manual