[Guix packaging] BeipDev/BeipMU #253

New issue

Closed

opened 2026-08-22 05:13:28 +00:00 by htayj · 2 comments

htayj commented

2026-08-22 05:13:28 +00:00

(Migrated from github.com)

Candidate

Canonical upstream: https://github.com/BeipDev/BeipMU
Packaging target: v331 (2026-02-17)
Category: MUD client
Tags: mud-client, desktop, Windows, Wine, MUSH, TLS
Primary language/build ecosystem: C++, Visual Studio/Windows APIs
License: MIT
License evidence: https://github.com/BeipDev/BeipMU/blob/master/LICENSE
Expected Guix packaging difficulty: hard

User-facing deliverable

Actively maintained open-source Windows MU* desktop client with TLS and text-game features.

Packaging approach

Investigate a reproducible MinGW cross-build and Wine wrapper from source, including fonts, audio, TLS, and writable user configuration.

Known blockers and investigation points

Windows-native build system and APIs; do not fall back to an opaque upstream executable without a separate nonfree-package decision.

Acceptance checks

Pin an immutable upstream release or commit and record a real Guix source hash.
Build without network access using Guix-provided dependencies; do not download runtimes or plugins during the build.
Preserve all applicable project and bundled-component license notices.
Verify the installed launcher/version output and run an offline protocol smoke test against a local fake MUD endpoint where the platform permits it.
Keep profiles, logs, maps, plugins, and other mutable state outside the store.

Existing-package coverage

Checked on 2026-08-22 against GNU Guix, Nonguix, Guix Science, Guix HPC, Guix Past, Guix R Us, and RDE, plus all states of this repository issue tracker. No same-upstream package or existing ticket was found. GNU Guix already packages TinTin++ and POWWOW; this candidate is distinct.

Imported from GitHub issue/PR. Originally posted by htayj on 2026-08-22T05:13:28Z.

## Candidate - Canonical upstream: [https://github.com/BeipDev/BeipMU](https://github.com/BeipDev/BeipMU) - Packaging target: v331 (2026-02-17) - Category: MUD client - Tags: mud-client, desktop, Windows, Wine, MUSH, TLS - Primary language/build ecosystem: C++, Visual Studio/Windows APIs - License: MIT - License evidence: https://github.com/BeipDev/BeipMU/blob/master/LICENSE - Expected Guix packaging difficulty: hard ## User-facing deliverable Actively maintained open-source Windows MU* desktop client with TLS and text-game features. ## Packaging approach Investigate a reproducible MinGW cross-build and Wine wrapper from source, including fonts, audio, TLS, and writable user configuration. ## Known blockers and investigation points Windows-native build system and APIs; do not fall back to an opaque upstream executable without a separate nonfree-package decision. ## Acceptance checks - Pin an immutable upstream release or commit and record a real Guix source hash. - Build without network access using Guix-provided dependencies; do not download runtimes or plugins during the build. - Preserve all applicable project and bundled-component license notices. - Verify the installed launcher/version output and run an offline protocol smoke test against a local fake MUD endpoint where the platform permits it. - Keep profiles, logs, maps, plugins, and other mutable state outside the store. ## Existing-package coverage Checked on 2026-08-22 against GNU Guix, Nonguix, Guix Science, Guix HPC, Guix Past, Guix R Us, and RDE, plus all states of this repository issue tracker. No same-upstream package or existing ticket was found. GNU Guix already packages TinTin++ and POWWOW; this candidate is distinct. --- Imported from [GitHub issue/PR](https://github.com/htayj/guix-channel/issues/253). Originally posted by [htayj](https://github.com/htayj) on 2026-08-22T05:13:28Z.

htayj commented

2026-08-22 13:05:42 +00:00

(Migrated from github.com)

Feasibility research is complete and BeipMU is blocked because the public repository is not a complete buildable source release.

Pin v331 commit 988cccac23369835b2647029a0fa02b42d69b91f, recursive NAR hash 10by8rj0x27dqkgvr1bcnvgxjxdq543wwfkzbawc8b3bx72krdpr.
The tag has no solution/project, CMake, Make, CI, dependency manifest, or submodules. Main.h immediately requires missing LibWin32, socket/TLS, Text, generated build/key headers, and at least 25 other absent internal/generated/dependency trees. These paths never existed in repository history and no public companion repository was found.
A real Guix MinGW syntax-build fails immediately on missing LibWin32/LibWin32.h. No downstream patch can reconstruct an omitted framework of this size.
The application is Windows-native C++ using Win32/COM, Direct2D/DirectWrite, SChannel, Media Foundation, SAPI/Tolk, ActiveScript/Chakra, and optional WebView2. A future Guix package would cross-build a Windows executable and wrap it in an XDG-scoped Wine prefix, not create a native Linux binary.
The official executable launched for a bounded 25 seconds under Wine/Xvfb and created APPDATA config with Version=331, establishing only basic runtime plausibility. The binary is verification evidence, not an acceptable package source.
Visible project code is MIT, but the missing framework/dependencies have unknown licenses. Emoji data in the binary release, maps, artwork and media lack per-file provenance. Keep needs:license-investigation.
TLS defaults certificate verification off. A future package must make that insecure mode explicit and prove trusted-CA success plus wrong-certificate rejection.
There is no test suite or CI.

Reopen only after upstream publishes complete framework/generator sources, reproducible build files, exact dependency pins/notices, generated resource steps, and asset provenance or replacements. Then first prove a network-isolated MinGW cross-build before packaging. WebView2 must remain optional/nonfatal and all Wine state must stay under XDG APPDATA.

No BeipMU package was found in the same-day GNU Guix, Nonguix, Guix Science/HPC/Past/R Us/RDE audit.

Imported from GitHub comment. Originally posted by htayj on 2026-08-22T13:05:42Z.

Feasibility research is complete and BeipMU is blocked because the public repository is not a complete buildable source release. - Pin v331 commit 988cccac23369835b2647029a0fa02b42d69b91f, recursive NAR hash 10by8rj0x27dqkgvr1bcnvgxjxdq543wwfkzbawc8b3bx72krdpr. - The tag has no solution/project, CMake, Make, CI, dependency manifest, or submodules. Main.h immediately requires missing LibWin32, socket/TLS, Text, generated build/key headers, and at least 25 other absent internal/generated/dependency trees. These paths never existed in repository history and no public companion repository was found. - A real Guix MinGW syntax-build fails immediately on missing LibWin32/LibWin32.h. No downstream patch can reconstruct an omitted framework of this size. - The application is Windows-native C++ using Win32/COM, Direct2D/DirectWrite, SChannel, Media Foundation, SAPI/Tolk, ActiveScript/Chakra, and optional WebView2. A future Guix package would cross-build a Windows executable and wrap it in an XDG-scoped Wine prefix, not create a native Linux binary. - The official executable launched for a bounded 25 seconds under Wine/Xvfb and created APPDATA config with Version=331, establishing only basic runtime plausibility. The binary is verification evidence, not an acceptable package source. - Visible project code is MIT, but the missing framework/dependencies have unknown licenses. Emoji data in the binary release, maps, artwork and media lack per-file provenance. Keep needs:license-investigation. - TLS defaults certificate verification off. A future package must make that insecure mode explicit and prove trusted-CA success plus wrong-certificate rejection. - There is no test suite or CI. Reopen only after upstream publishes complete framework/generator sources, reproducible build files, exact dependency pins/notices, generated resource steps, and asset provenance or replacements. Then first prove a network-isolated MinGW cross-build before packaging. WebView2 must remain optional/nonfatal and all Wine state must stay under XDG APPDATA. No BeipMU package was found in the same-day GNU Guix, Nonguix, Guix Science/HPC/Past/R Us/RDE audit. --- Imported from [GitHub comment](https://github.com/htayj/guix-channel/issues/253#issuecomment-5380566378). Originally posted by [htayj](https://github.com/htayj) on 2026-08-22T13:05:42Z.

htayj commented

2026-08-22 17:20:11 +00:00

(Migrated from github.com)

Closing as not planned. Reopen when upstream publishes the complete framework and generators, reproducible build files, fixed dependency sources/notices, and asset provenance.

Imported from GitHub comment. Originally posted by htayj on 2026-08-22T17:20:11Z.

Rechecked current head 3d43fe9327e18dcc30a38b2f7422f558b95a4c3c. The repository still lacks build metadata and the internal framework/generated headers required by Main.h; the latest commit only adds sound implementation files. This is not reconstructible downstream as a packaging patch. Closing as not planned. Reopen when upstream publishes the complete framework and generators, reproducible build files, fixed dependency sources/notices, and asset provenance. --- Imported from [GitHub comment](https://github.com/htayj/guix-channel/issues/253#issuecomment-5381643621). Originally posted by [htayj](https://github.com/htayj) on 2026-08-22T17:20:11Z.