aboutsummaryrefslogtreecommitdiffstats
path: root/contrib/homebrew (follow)
Commit message (Collapse)AuthorAge
* brew: pin the build to zig@0.16HEADmasterPeter Geissler8 days
| | | | | | | | | | | homebrew-core moved "zig" to 0.17.0, and the vendored libghostty-vt rejects any mismatched major/minor, so every brew install broke with "Your Zig version v0.17.0 does not meet the required build version of v0.16.0". Installing zig@0.16 by hand did not help: it is keg-only, so it is never on PATH, and the formula took the "zig" opt path regardless. Also stop hardcoding the version in the test block; it had gone stale at 0.1.0 and failed against the 0.1.8 binary.
* release: v0.1.8 paperwork -- formula and PKGBUILD pinneduser2026-09-22
|
* release: v0.1.7 paperwork -- formula and PKGBUILD pinneduser2026-09-10
|
* release: v0.1.6 paperwork -- formula and PKGBUILD pinneduser2026-09-07
|
* release: v0.1.5 paperwork -- formula and PKGBUILD pinneduser2026-09-02
|
* release: v0.1.4 paperwork -- formula and PKGBUILD pinneduser2026-09-02
|
* arch-repo: find zig on PATH itself; release: v0.1.3 paperworkuser2026-09-02
| | | | | | | | | 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.
* public links: point at github.com/sl0p-foo/slosh instead of cgituser2026-09-02
| | | | | | | | 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.
* brew: pin formula to v0.1.2user2026-09-02
|
* point homebrew tap at github.com/sl0p-foo/homebrew-sloshuser2026-09-02
| | | | | brew auto-resolves GitHub taps, so the explicit URL is no longer needed: 'brew tap sl0p-foo/slosh' is all users type.
* slosh(5): the file formats get their manpage; slosh(1) learns shadersuser2026-08-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Section 5 is where unix keeps its file formats, and slosh has two documents sharing one syntax -- the configuration and the layouts -- so they share a page the way they share a parser. docs/slosh.5 covers the KDL subset, where the file lives and how reload refuses a broken one, include and its precedence, every top-level setting grouped the way config.md groups them, the theme block, the shader vocabulary with the expression language summarised, the states and their ranking, the keys block including direct bindings, and the layout schema (tab, pane, and their properties). Held to the source like slosh.1 before it: every name in config.c's KNOWN_TOP -- the list the loader refuses unknown settings against, itself held to the loader by test_config.py -- must appear in the page, so a knob cannot be added without this page hearing about it. The pair must cross-reference each other, and both must be pure ASCII and lint clean under groff -ww. slosh(1) grows a SHADERS section -- the one feature a synopsis reader would never guess a multiplexer had -- and its SEE ALSO now names slosh(5) and nothing else: the other multiplexers can advertise themselves. Install puts the page under share/man/man5, the release tarballs carry both pages, and the Homebrew formula installs what the commit it is building has, guarded as before.
* a manpage: slosh(1), installed, shipped, and held to the sourceuser2026-08-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | The distributables were a bare binary and a directory of Markdown, which is fine until somebody types 'man slosh' -- the unix-traditional place to ask. docs/slosh.1 is hand-written man(7), pure ASCII roff, no toolchain: the synopsis, the options, the session commands, the default keys, the mouse (including the new drag-past-an-edge scrolling), where the configuration lives, what SLOSH_* means in a pane's environment, files, exit status. The prose docs stay the long form; the page says so and points at them. 'make install' puts it under PREFIX/share/man/man1 (and uninstall takes it away), the release tarballs carry it beside the LICENSE -- a tarball is what a packager starts from -- and the Homebrew formula installs it when the commit it is building has one, guarded because the formula must be able to build commits older than the page. Prose about a program drifts unless something holds them together, so test_docs.py holds the page to the source the way it already holds the site to docs/nav: every option main.c's parser compares against and every word command must appear in the page, every SLOSH_* variable the code reads or sets must be documented, the roff must be pure ASCII (it travels through implementations that never heard of preconv), and where groff exists the page must lint clean at CHECKSTYLE=3 with -ww. Adding a flag without documenting it is now a failing test, which is the only kind of documentation policy that survives contact with a deadline.
* brew-release: cut a release from the Linux box it is cut fromPeter Geissler2026-08-26
| | | | | | | | | | | | | | | | | | | | Nothing about updating the formula needs a mac or needs brew -- it resolves a ref, fetches a tarball, hashes it, rewrites three stanzas. But it hashed with `shasum`, which is perl's and only usually present on Linux, where `sha256sum` is coreutils and always is. Take whichever exists, as macos-remote-build already did. The version count no longer falls back to 0 when the commit is not in this clone. `0.1.0-0-<short>` is older than every version published, so a release cut from a clone that had not fetched yet would have looked like a downgrade and never installed; say so and stop instead. Also written down: why the formula builds from source rather than shipping the notarized zip the mac builder makes -- brew's curl sets no quarantine attribute, so notarization gains a formula nothing, and the build is a minute with zig as its only dependency. If that ever changes the answer is bottles, which are additive and cost a per-macOS-version matrix, not a cask.
* homebrew: a formula, and a script that keeps it honestPeter Geissler2026-08-26
`brew install slosh` is the shortest install there is, and the formula is small because `make install` already does the work: zig as the only build dependency, both zig caches redirected into the build directory so the sandbox does not deny them and the user's real cache is not polluted, and the commit id handed to the Makefile because a snapshot tarball has no .git for `git describe` to read. The url/version/sha256 triple is the part that rots. contrib/brew-release resolves a ref to a full commit id, fetches the cgit snapshot, hashes what it actually got, and rewrites those three stanzas -- it does not commit or push, so the diff is read by a human first. Untagged pins carry the commit count so `brew upgrade` can tell newer from older; alphabetical comparison of two short ids cannot. The formula lives here as the source of truth and is copied into the tap; contrib/homebrew/README.md says why it is a formula and not a cask, and what still stands between this and homebrew-core.