初始提交:terminalX 可运行态(M0/M1/M1.5 已真机验证)
- M0: libghostty SSH 终端(渲染/输入/连接)+ 白屏修复(OutputGate) + 会话状态机/自动重连 - M1: tsnet 用户态组网 + SSH-over-tsnet(fd 桥),shell 级真机验证;R5(Go+gvisor+C+++Swift 同进程) retire - M1.5: tmux -CC 原生 tab(MVP) - 结构: packages/(TXCore·TXTransport), apps/TerminalX, vendor/(libghostty-spm/libssh2/mbedtls/tsnet-bridge), artifacts/ - 文档: CLAUDE.md + docs/HANDOFF.md(新会话入口) - 环境: 认证代理→依赖 vendor 本地化;Go 在 ~/.local/go;仅模拟器/未签名 - 待续: M2 mosh, tmux 多 pane, M4 安全(host key/SE) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
25
vendor/libghostty-spm/Patches/ghostty/README.md
vendored
Normal file
25
vendor/libghostty-spm/Patches/ghostty/README.md
vendored
Normal file
@@ -0,0 +1,25 @@
|
||||
# Ghostty Patches
|
||||
|
||||
This directory is the single place for local upstream Ghostty patches used by
|
||||
the `libghostty-spm` build pipeline.
|
||||
|
||||
## Rules
|
||||
|
||||
- Keep patches numbered so they apply in a stable order.
|
||||
- Prefer standard unified diff files (`.patch`) when the upstream context is
|
||||
stable.
|
||||
- Use executable patch scripts (`.sh`) only when upstream context is too
|
||||
unstable for a reliable diff.
|
||||
- Keep version-specific variants beside the original patch and select them in
|
||||
`Script/apply-patches.sh` using an upstream API marker.
|
||||
- Preserve newer Ghostty's renamed internal-library outputs when extending its
|
||||
Darwin static-library build path.
|
||||
- Every patch in this directory must be safe to re-run.
|
||||
- Patches here are applied automatically by `Script/build-ghostty.sh`, so they
|
||||
affect macOS, iOS, and Mac Catalyst builds equally.
|
||||
|
||||
## Current goal
|
||||
|
||||
This patch workflow exists so we can carry host-managed IO work required for
|
||||
sandboxed iOS, macOS, and Mac Catalyst integration without hiding upstream
|
||||
modifications inside ad-hoc build script edits.
|
||||
Reference in New Issue
Block a user