pkg.soopen package index

brew / 排名 20534

使用 Homebrew 安装 tundra

查看 tundra 的安装路径、可执行文件、元数据以及面向 AI 代理工作流的安全说明。

安装

其他安装命令

macOS

Homebrew已验证 · 100%
brew install tundra

local Homebrew formula metadata

概览

软件包摘要

Code build system that tries to be fast for incremental builds

命令和别名

  • t2-inspect
  • t2-lua
  • tundra2

历史

项目历史与用法

Tundra is a high-performance code build system by Andreas Fredriksson, designed for very fast incremental builds in large software projects. Its manual says the design was motivated by games industry workloads, where large multi-million-line codebases and frequent rebuilds make every second of build-system overhead expensive.

项目历史

The README and manual present Tundra as a deliberately scoped build system: a Lua configuration front end builds dependency graphs, while a native multi-threaded build engine executes commands. The Lua front end runs only when needed, leaving incremental build iteration to a fast engine.

Tundra's design philosophy is unusually explicit. It favors "simple is fast", "support just enough", multi-core utilization, reliable code generation through build passes, separation between configuration and building, and avoiding toolchain guessing. This sets it apart from broader build tools that fetch code, auto-detect environments, or hide platform choices.

The README identifies copyright from 2010 to 2018 and notes that Tundra was previously GPL-licensed before being relicensed to MIT because the GPL hindered commercial adoption and contributors agreed to the change. That license history is a direct clue to its intended use in commercial native-code projects.

采用历史

Official docs describe portability across macOS, Linux, FreeBSD, and Windows, with Windows installers in GitHub releases and Homebrew as the macOS package path. The input package facts record Homebrew packaging, and the formula installs CLI tools such as `tundra2`, `t2-lua`, and `t2-inspect`.

Tundra's adoption niche is not broad web development but native-code teams that care about fast incremental rebuilds, explicit toolsets, and generated-code ordering. The manual's games-industry motivation explains why package users encounter it alongside build systems like Make, Ninja, SCons, Premake, CMake, and Tup rather than as an application.

使用方式

A Tundra project is driven by a `tundra.lua` file, analogous to a Makefile, that declares units and configurations. The manual's hello-world example defines a Build block with Units and Configs, then runs `tundra2` to build into a platform, toolset, variant, and subvariant output directory.

The build flow is split into graph generation and execution: `tundra2` checks whether DAG data is up to date, invokes the Lua generator if needed, saves a JSON graph for compiled binary data, deletes stale outputs, analyzes requested targets, runs the build engine, and saves build state.

为什么软件包爱好者会关心

Tundra is significant to package nerds because it is a small, fast, specialist alternative in the build-system zoo. It exposes enough machinery for serious native builds while avoiding package downloaders, VCS sync, and toolchain guessing, which appeals to users who prefer explicit, reproducible build descriptions.

Its Homebrew formula makes a historically source-oriented build tool easy to install on macOS, while the manual preserves the deeper Unix build-system culture: one configuration file, named toolsets, variants, generated DAGs, and inspectable command execution.

时间线

  • 2010-2018: README copyright range identifies Andreas Fredriksson's project history window.
  • Current README: Documents macOS, Linux, FreeBSD, and Windows portability, plus Homebrew installation for macOS.
  • Current README: Notes relicensing from GPL to MIT to improve commercial adoption.
  • Current manual: Documents Lua front end, native build engine, build passes, and `tundra.lua` project files.

Related projects

  • Lua 5.1 is embedded and customized as the configuration language.
  • The manual's design context places Tundra near Make-style tools and native build systems; its explicit non-goals distinguish it from build systems that fetch dependencies or auto-configure environments.
  • A companion Visual Studio 2012 add-in is linked from the README at https://github.com/deplinenoise/tundra-vsplugin.

安全态势

风险级别:yellow

generalized runtime or code generation signal.

风险分类器

yellow 风险 · 中 置信度 · runtime

原因

  • generalized runtime or code generation signal

信号

  • text:build system

安装行为

  • formula 元数据中未记录 Homebrew post-install 钩子。
  • Homebrew bottle 元数据适用于 8 个平台目标。
  • 构建元数据列出 1 个构建依赖。

建议审查

在无人值守的代理使用前,请检查该工具是否读取明文凭据、写入远程状态、发布制品或调用插件。

local files

Configuration and credential file locations

These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.

Configuration files

Config paths the tool may read or write during local use.

Unix
tundra.lua

可执行文件

已安装的可执行文件

命令类型暴露范围备注
t2-inspectcli全局可执行文件
t2-luacli全局可执行文件
tundra2cli全局可执行文件

新鲜度

版本和新鲜度

这些信号区分页生成时间、软件包管理器活动和上游发布比较。只有存在证据 URL 和可比较版本时,才会提示版本落后。

页面生成时间2026-08-04
管理器版本2.17.1
管理器更新时间2026-06-25
本地数据OK
上游当前
检测到的最新版本v2.17.1

https://github.com/deplinenoise/tundra

  • OK没有生成新鲜度警告。

安装元数据

软件包元数据

软件包键brew:tundra
版本2.17.1
软件包管理器Homebrew
软件包管理器页面https://formulae.brew.sh/formula/tundra
主页https://github.com/deplinenoise/tundra
仓库https://github.com/deplinenoise/tundra
许可证MIT
源码归档https://github.com/deplinenoise/tundra/archive/refs/tags/v2.17.1.tar.gz
最后更新2026-06-25T13:38:10+02:00
Pulseupdated
构建依赖googletest
Bottle可用 (于 arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, sonoma, ventura, x86_64_linux)
Homebrew post-install未定义
服务未声明

注册表事实

源数据库详情

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

来源线索

由仓库数据生成

此页面由 av-webscripts/generate-pkg-sqlite.py 生成的私有软件包 SQLite 工件提供。

使用的来源

  • Geiger risk classifier
  • cross-ecosystem install command graph
  • curated configuration and credential file locations
  • curated package history
  • package relationship graph
  • package version freshness
  • package-page enrichment
  • pkg.so package database
  • pkgdb category and tag curation