Skip to content

Add gomoku-rm 1.0.1#177

Open
jiafans wants to merge 2 commits into
vellum-dev:mainfrom
jiafans:add-gomoku-rm
Open

Add gomoku-rm 1.0.1#177
jiafans wants to merge 2 commits into
vellum-dev:mainfrom
jiafans:add-gomoku-rm

Conversation

@jiafans

@jiafans jiafans commented May 8, 2026

Copy link
Copy Markdown

Adds gomoku-rm 1.0.1 — a Gomoku (五子棋) game for reMarkable 2.

Pure-Rust app built on libremarkable 0.7, runs as an AppLoad external with qtfb-shim (same setup as vnsee-qtfb). Self-implemented Alpha-Beta engine: negamax + iterative deepening + candidate pruning + 3s time budget; depth 2/4/6 across 3 difficulty levels. 19×19 board with Go-style coordinates.

Local checks both PASS:

  • scripts/validate-velbuild.sh
  • scripts/lint-packages.sh

Notes:

  • arch=\"armv7\" only — the upstream repo includes vendored patches to libremarkable and evdev that are specifically for the rM2 multitouch quirks (no ABS_MT_PRESSURE; BTN_TOUCH without EV_KEY). Aarch64 (rM Paper Pro) builds aren't validated yet.
  • Installs to /home/root/xovi/exthome/appload/gomoku/
  • postdeinstall honors VELLUM_PURGE=1 to also remove /home/root/.config/gomoku-rm/ (savestate + config)

Gomoku (五子棋) game for reMarkable 2 — pure Rust + libremarkable + AppLoad
with a self-built Alpha-Beta engine. 19×19 board, 3 difficulty levels,
bilingual UI scaffolding, persistent saves.

Verified working end-to-end on rM2 firmware 20260210094933.
Source: https://github.com/jiafans/gomoku-rm  (MIT)
Release: https://github.com/jiafans/gomoku-rm/releases/tag/v1.0.1

scripts/validate-velbuild.sh + scripts/lint-packages.sh both PASS locally.
Comment thread packages/gomoku-rm/VELBUILD Outdated
maintainer="jeffrey <jeffrey@shaojia.fan>"
pkgname=gomoku-rm
pkgver=1.0.1
pkgrel=1

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
pkgrel=1
pkgrel=0

pkgrel in apk starts at 0

Comment thread packages/gomoku-rm/VELBUILD Outdated
@rmitchellscott

Copy link
Copy Markdown
Member

/publish-testing

@github-actions

github-actions Bot commented May 8, 2026

Copy link
Copy Markdown

Packages published to testing repo:

  • gomoku-rm

Install with:

vellum add gomoku-rm@testing

@rmitchellscott

Copy link
Copy Markdown
Member

Tested on rm1 as well.

@jiafans Please re-request a review once you've addressed my previous review. Feel free to test from the Vellum testing repo as well if you want, instructions in the Vellum README.

- pkgrel: 1 → 0 (apk convention: first packaging of a pkgver starts at 0)
- drop postdeinstall block: vellum auto-removes tracked install paths;
  /home/root/.config/gomoku-rm/ is user data and shouldn't be wiped on
  uninstall (matches rmstream / vnsee convention)
@jiafans

jiafans commented May 15, 2026

Copy link
Copy Markdown
Author

@rmitchellscott Thanks for the review and for publishing to testing! Addressed both points in b12c0ed:

  • pkgrel: 10. Got it — first packaging of a pkgver starts at 0 per apk convention.
  • postdeinstall: removed the whole block. After re-reading the suggestion + comparing with rmstream's and vnsee-qtfb's VELBUILD, agreed that vellum already auto-removes tracked install paths, and /home/root/.config/gomoku-rm/ is user data (savestate / config) that shouldn't be wiped on uninstall.

Local scripts/validate-velbuild.sh + scripts/lint-packages.sh both PASS on the new commit. The CI run is sitting in action_required — could you re-approve the workflow when you have a sec? Happy to re-request the formal review once it's runnable (I don't have triage permission to re-request directly).

@rmitchellscott

Copy link
Copy Markdown
Member

/publish-testing

@github-actions

Copy link
Copy Markdown

Packages published to testing repo:

  • gomoku-rm

Install with:

vellum add gomoku-rm@testing

@rmitchellscott

Copy link
Copy Markdown
Member

@jiafans bump

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants