Skip to content

Install the omarchy(1) man page - #200

Open
aleksejunas wants to merge 1 commit into
omacom:masterfrom
aleksejunas:man-page-install
Open

Install the omarchy(1) man page#200
aleksejunas wants to merge 1 commit into
omacom:masterfrom
aleksejunas:man-page-install

Conversation

@aleksejunas

Copy link
Copy Markdown

PR mot omacom-io/omarchy-pkgs (branch: man-page-install)

Tittel

Install the omarchy(1) man page

Beskrivelse

Companion to omacom/omarchy#8064: that PR generates man/man1/omarchy.1
in the source repo (see its tools/man-gen/). This just installs the
already-generated file to the standard path:

install -Dm644 man/man1/omarchy.1 "$pkgdir/usr/share/man/man1/omarchy.1"

Nothing is built here — the man page ships as committed in the source tree
at whatever _commit this PKGBUILD points at.

Sequencing

This will fail to build against the current _commit (286b8c2b...), since
that predates the man page existing in the source repo. This only needs to
land — or just be bumped in — once _commit here is updated to a commit
that includes man/man1/omarchy.1. Flagging this so it doesn't get merged
and immediately break a build; happy to hold this until after the other PR
merges and a release is cut, whatever's easiest for you.

The omarchy source repo now generates man/man1/omarchy.1 from
`omarchy commands --all --json` (see basecamp/omarchy's tools/man-gen).
This just installs the already-generated file to the standard man path;
it doesn't run the generator during the package build.

Depends on _commit here being bumped to (or past) the commit that adds
man/man1/omarchy.1 in basecamp/omarchy — this line will fail the build
against any pinned commit that predates it.
@greptile-apps

greptile-apps Bot commented Aug 24, 2026

Copy link
Copy Markdown

Greptile Summary

Adds the generated omarchy(1) manual page to the main Omarchy package.

  • Installs man/man1/omarchy.1 under /usr/share/man/man1/ with standard read-only permissions.
  • Documents that the generated page is consumed from the pinned upstream source rather than rebuilt during packaging.

Confidence Score: 5/5

The packaging change appears safe to merge when applied with the explicitly required upstream source revision.

The install destination and permissions follow the standard man-page layout, and the only current build constraint is already documented as an intentional sequencing requirement.

Important Files Changed

Filename Overview
pkgbuilds/omarchy/PKGBUILD Adds a conventional package-stage installation step for the upstream-generated manual page; no unacknowledged actionable issue was identified.

Reviews (1): Last reviewed commit: "Install the omarchy(1) man page" | Re-trigger Greptile

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant