Repository navigation
Arch/Omarchy package, and both packaging files on v0.2.0 - #3
Merged
Merged
Conversation
Omarchy is Arch (ID_LIKE=arch, same pacman), so one package covers both and there is no separate Omarchy artifact to keep in sync. Shaped after the omarchy-pkgs house style: cargo fetch --locked in prepare() so build() and check() can run --frozen, !debug because nobody attaches a debugger to a statusline segment, and both LICENSE texts because MIT OR Apache-2.0 is the consumer's choice, not a conjunction. check() runs the suite against the release binary — tests/cli.rs is process-level, so it has to be the same binary package() installs. .SRCINFO is deliberately not kept here: it is generated, only the AUR repo needs it, and a copy in this tree would go stale on the first bump.
v0.2.0 is tagged now, so the formula and the PKGBUILD both point at it. Same tarball, same sha256.
The README calls this file the source of truth for the tap, but the tap had drifted ahead: 0533a08 there tightened the test block to assert the exact 13-cell and dense renderings, the statusline stdin path, and the unknown-subcommand exit, and that never came back here. Copying this file over the tap — which is what the README tells you to do on a release — would have quietly reverted it. Below the header comment the two files are now byte-identical.
tlehman
force-pushed
the
arch-packaging
branch
from
September 2, 2026 14:34
02077d6 to
0e93edf
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds
packaging/arch/PKGBUILDnext to the Homebrew formula, so dotbar installs on Arch — and therefore on Omarchy, which is Arch with the same pacman, so there is no second artifact to keep in sync.Shape follows the omarchy-pkgs house style (
ttfx):cargo fetch --lockedinprepare()sobuild()andcheck()run--frozen,options=('!debug'),depends=('gcc-libs' 'glibc').check()runs the suite against the release binary, sincetests/cli.rsis process-level and has to exercise the binarypackage()installs. Both LICENSE texts ship:MIT OR Apache-2.0is a choice, not a conjunction..SRCINFOis not in the tree on purpose — it is generated, only the AUR repo needs it, and a copy here would go stale on the first bump. The PKGBUILD header carries the publish and release-bump procedure.The second commit moves the Homebrew formula to
v0.2.0, which is now tagged, so both packaging files sit on the same tag.Verified on an Omarchy 4.0.2 box:
makepkgbuilds from the real v0.2.0 tarball, all 26 tests pass incheck(), and the package containsusr/bin/dotbarplus both licenses and the README. The installed binary renders (NO_COLOR=1 dotbar --dense 76→⣿⡿⣀ 76%), exits 0 with no output on{}, and carriesinstall-claude.