an opinionated terminal multiplexer in C with programmable pane chrome https://git.sl0p.foo/slosh.git/atom/contrib/arch?h=master 2026-09-22T14:21:23Z 2026-09-22T14:21:23Z user user@clank 2026-09-22T14:21:23Z urn:sha1:dfdd8199da35f94ae6e81251b1489cb33d6c1504 2026-09-10T09:13:44Z user user@clank 2026-09-10T09:13:44Z urn:sha1:d9a04772fc4797ff20dccefc6cc4f68c6c040feb 2026-09-07T14:40:41Z user user@clank 2026-09-07T14:40:41Z urn:sha1:e918e4385c5e5cf944af53932f9a60eca03c1ac0 2026-09-02T14:40:32Z user user@clank 2026-09-02T14:40:32Z urn:sha1:abc2ee66fac8112c204e1f10df6741b4af25c416 optdepends says it at install time, the README and the install tab say it before. Our package deliberately does not ship the file: extra/ghostty-terminfo owns that path, and two packages must not. Without either, slosh's own ~/.terminfo copy covers it. pkgrel=2, both architectures rebuilt and republished. 2026-09-02T14:31:12Z user user@clank 2026-09-02T14:31:12Z urn:sha1:c534bee1dc7bb2c9929ca6a7e2d2af3fea17eaad 2026-09-02T14:10:48Z user user@clank 2026-09-02T14:10:48Z urn:sha1:9cc6ff911ac794c5831407358fddb7b7c9c24ef6 The v0.1.4 arch packages introduced themselves as 0.1.4-dirty: the tag's tarball has no .git, makepkg builds it inside the release box's repository, and git describe walked up and answered for the outer tree -- mid-release, when the paperwork is honestly dirty. Found at 0.1.2, diagnosed, and then left unfixed by yours truly. Two fences now. contrib/version only trusts a .git whose toplevel is its own root (helps every future tarball). The PKGBUILD exports GIT_CEILING_DIRECTORIES for build and package (helps regardless of which contrib/version the pinned tarball carries, which is why the first rebuild still said -dirty: the fix was outside the tarball). pkgrel=3; both architectures rebuilt, verified 'slosh 0.1.4', and republished. 2026-09-02T13:57:00Z user user@clank 2026-09-02T13:57:00Z urn:sha1:0280bc0635cb02ff8a96be7f5d730fee9161c307 2026-09-02T13:26:52Z user user@clank 2026-09-02T13:26:52Z urn:sha1:5dfb761d3060bff5be8623272fdaf0eeb27706ca ship calls arch-repo without the ZIG= prefix the by-hand runs had, so the leg died on makepkg's dependency check mid-release. arch-repo now derives ZIG from PATH when pacman has no zig, and exports it. The formula and PKGBUILD pins ride along: ship's steps 6 and 7 had already written them when the leg failed, and its preflight rightly refuses a dirty tree. 2026-09-02T12:43:09Z user user@clank 2026-09-02T12:43:09Z urn:sha1:18d1aef0f9bf4620135fd9f77f26683e6f2f8c00 The static musl release builds cannot dlopen -- musl compiles it out -- so loadable shader plugins were a feature most shipped binaries could not use. Nothing we ship used it either: every shader in contrib/shaders is an expression. Gone: the dlopen/glob loader in shader.c, shader_dir in the config, the plugin ABI table and entry macro, the Windows dl*/glob shims that existed only for it, the contrib/shader-plugin skeleton, its tests, and every doc mention. shader_abi.h stays as the shader model (cell_t, shade_ctx_t, shader_t) with a note about what it used to be. 2026-09-02T12:07:37Z user user@clank 2026-09-02T12:07:37Z urn:sha1:597135f7851e83e31d99fc9c97fbb087c3df4fce GitHub is the public interaction point now. The formula and PKGBUILD fetch GitHub's /archive/ tarballs (same git-archive bytes, per-ref stable); the PKGBUILD is bumped to 0.1.2 while at it, and its cd's drop the v -- GitHub tag archives extract to slosh-X.Y.Z/. The cgit remote stays for pushing; only published URLs change.