Skip to content

Rename the product to Retro, and follow recomp-ui to the org - #341

Open
TechnicallyComputers wants to merge 1 commit into
masterfrom
chore/retro-rename
Open

Rename the product to Retro, and follow recomp-ui to the org#341
TechnicallyComputers wants to merge 1 commit into
masterfrom
chore/retro-rename

Conversation

@TechnicallyComputers

Copy link
Copy Markdown
Collaborator

Follow-on to #340, which moved the submodule URLs. Two things have changed since it merged.

The product is Retro now. The launcher and studio ship as Retro Launcher and Retro Studio, so the old name is gone from display text, docs and generated READMEs.

recomp-ui moved to the org. mstan/recomp-uiRetroPortingToolKit/recomp-ui, so the scaffolder defaults and docs follow it. psxrecomp itself has not moved and is untouched.

The split is by case, and it is not cosmetic

CamelCase RetComM was always the product. Lowercase retcomm and RETCOMM_ are identifiers — the namespace, binaries, data directories, CMake and environment variables, readme markers. Renaming those orphans existing installs for no benefit, so they are untouched.

Three things are deliberately still spelled RetComM

  • RetComM-Data is CamelCase but it is a directory on disk (<exe_dir>\RetComM-Data\{runtime,config,data} for a portable install). Renaming it strands every portable user's config, toolchains and catalog cache.
  • TechnicallyComputers/RetComM-Launcher in readme_has_launcher() is the historical half of a both-slugs test. Renaming it duplicates the line above and reports every pre-transfer port as missing its launcher section.
  • _LEGACY_LAUNCHER_RE matched ^## RetComM Launcher. The sweep renamed it, which would have silently stopped it matching every README already out there — it now accepts both headings.

Verification

bash -n on the scaffolders; every touched .py compiles; and the README machinery checked directly:

old heading: True    new heading: True
old slug   : True    new slug   : True
generated block heading: ## Retro Launcher

🤖 Generated with Claude Code

https://claude.ai/code/session_013DpaQqVguHFpBuCmdoFYWY

The launcher and studio ship as Retro Launcher and Retro Studio now,
from the RetroPortingToolKit org, so the old product name is gone from
display text, documentation and release asset filenames.

The split is by case, and it is not cosmetic. CamelCase RetComM was
always the product; lowercase retcomm and RETCOMM_ are identifiers --
the C++ namespace, the binaries, the data directories, the CMake and
environment variables, the Cloudflare service names, the readme markers.
Renaming those would orphan existing installs for no benefit, so they
are untouched: 1101 lowercase retcomm and 205 RETCOMM_ still stand in
the launcher alone.

Four things are deliberately still spelled RetComM, and three of them
would have been real breakage:

- RetComM-Data is CamelCase but it is a directory on disk --
  <exe_dir>\RetComM-Data\{runtime,config,data} for a portable install.
  Renaming it strands every portable user's config, toolchains and
  catalog cache.

- TechnicallyComputers/RetComM-Launcher in readme_has_launcher() is the
  historical half of a both-slugs test. Renaming it makes it a duplicate
  of the line above and sends every port built before the transfer back
  to reporting its launcher section missing.

- _LEGACY_LAUNCHER_RE matched "^## RetComM Launcher". A sweep renamed it,
  which would have silently stopped it matching every README already out
  there; it now accepts both headings.

- The portable-stub lookup gained the pre-rename filenames back as
  fallbacks, because old zips stay on the releases page and a rollback
  downloads one.

Release assets become Retro-Launcher-* / Retro-Studio-*. That is safe
for installed clients: pick_launcher_asset() gates on *linux*/*windows*/
*macos* plus extension and arch, not on the product name, and the
Windows portable stub is identified by its RCM1 trailer rather than its
filename.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013DpaQqVguHFpBuCmdoFYWY
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