<feed xmlns='http://www.w3.org/2005/Atom'>
<title>slosh.git/contrib/version, branch master</title>
<subtitle>an opinionated terminal multiplexer in C with programmable pane chrome</subtitle>
<id>https://git.sl0p.foo/slosh.git/atom/contrib/version?h=master</id>
<link rel='self' href='https://git.sl0p.foo/slosh.git/atom/contrib/version?h=master'/>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/'/>
<updated>2026-09-02T14:10:48Z</updated>
<entry>
<title>version: never answer for somebody else's git; arch: 0.1.4-3</title>
<updated>2026-09-02T14:10:48Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-09-02T14:10:48Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/commit/?id=9cc6ff911ac794c5831407358fddb7b7c9c24ef6'/>
<id>urn:sha1:9cc6ff911ac794c5831407358fddb7b7c9c24ef6</id>
<content type='text'>
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.
</content>
</entry>
<entry>
<title>release: one 'make release' for the three target binaries</title>
<updated>2026-08-26T23:28:45Z</updated>
<author>
<name>user</name>
<email>user@clank</email>
</author>
<published>2026-08-26T23:28:45Z</published>
<link rel='alternate' type='text/html' href='https://git.sl0p.foo/slosh.git/commit/?id=5ba81343523e7b56a1514f2fc98f47973299b8f4'/>
<id>urn:sha1:5ba81343523e7b56a1514f2fc98f47973299b8f4</id>
<content type='text'>
Streamline the release into a single target that stages all three binaries
in dist/ with a SHA256SUMS:

  linux x86_64  }  cross-built here with 'zig cc -target ... -s', static musl
  linux aarch64 }  (runs on any distro), packaged as a .tar.gz with the binary
                   + README + LICENSE + THIRD-PARTY-LICENSES
  macos arm64      handed to 'macos-dist', which signs/notarizes on the builder

zig is already the compiler, so the two linux cross-builds need no extra
toolchain -- just the vendored libghostty-vt rebuilt per -Dtarget. Verified
both: static, stripped (~2MB), and both run (aarch64 under qemu-user).

Factor the version ladder out of the Makefile into contrib/version, and call
it from both Makefile and Makefile.macos, so the linux tarballs, the signed
zip and the binary's own --version are all named from the same tag instead
of Makefile.macos using its own 'git describe --always' scheme (which would
have named the mac artifact after a bare commit hash while linux used the
tag).

  make release-linux            # just the two linux tarballs
  make release REF=&lt;tag&gt;        # all three + SHA256SUMS
</content>
</entry>
</feed>
