Skip to content

0.23.0: dist-deb and dist-rpm, the staged tree as a Debian or RPM package - #56

Merged
Sunrisepeak merged 2 commits into
mainfrom
dist-deb-rpm
Nov 18, 2026
Merged

Sunrisepeak merged 2 commits into
mainfrom
dist-deb-rpm

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

Adds two dist members, dist-deb and dist-rpm, and bumps the package to 0.23.0.

  • Both install the tree mcpp pack stages, unchanged, under /opt/<name>, with /usr/bin/<name> execing the tree's launcher, a desktop entry, and an optional PNG or SVG icon. Control fields come from [package]; a package without a maintainer is refused rather than published under a guessed name. options::depends lists packages the machine provides.
  • The layout lives in dist/linux-package.cppm (mcpp.dist.linux_package, feature dist-linux-package, implied by both); dist/deb.cppm and dist/rpm.cppm are thin members with the usual plan_for/submit/generate.
  • The writer is nfpm from xim:nfpm (feat(nfpm): add 2.49.0 for linux/macosx/windows x86_64+aarch64 with automatic updates openxlings/xim-pkgindex#1186, merged), declared on the cfg(linux) axis with provision = "on-request", so no host needs dpkg-deb or rpmbuild and a build that packs nothing downloads nothing.
  • Every staged file is listed with an explicit mode and SOURCE_DATE_EPOCH (or a fixed time): measured on nfpm 2.49.0, tree entries keep source mtimes and the top-level mtime does not reach them.

Fixture tests/linux-package-consumer; the new CI step checks that a plain build produces no package, that --pkg-format bogus names both formats, the deb's control fields and the rpm's requirement, that both packages carry the same files, installs the deb and runs the program, and that repacking an unchanged tree gives identical bytes.

Local results on Linux x86_64 with a downloaded nfpm 2.49.0 passed as options::tool: both packages produced, fields and file lists as above, the program runs from the extracted package, and repacking is byte-identical. Resolving xim:nfpm from the index was not verified locally: the index artifact mcpp synced predates #1186. The README floor 2026.10.30.1 is the package's existing floor; the members use no newer engine API.

…kage

Both members install the tree mcpp pack stages under /opt/<name>, with a
launcher in /usr/bin, a desktop entry and an icon, and take the control fields
from [package]. They share mcpp.dist.linux_package and write either format
with nfpm from the xim:nfpm payload, asked for only when a pack needs it, so
no host needs dpkg-deb or rpmbuild. Every staged file is listed with an
explicit mode and time, so repacking an unchanged tree gives the same bytes.
tests/linux-package-consumer packs both, compares their contents, installs
the deb and runs the program.
…every host

The collection states its version in src/plugins.cppm as well as mcpp.toml,
and tests/all-rules-compile names every member that carries sources, so both
new members' plans are compiled and asserted silent on macOS and Windows.
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