Repository navigation
Conversation
The build repository was renamed gershwin-build -> gershwin-developer. The old
URL still redirects, so the nine references across five pages looked fine while
two of them handed the reader commands that fail.
building.md and rpi.md both said:
cd gershwin-build
./bootstrap.sh
The scripts live in Library/Scripts/, so that is an immediate "No such file or
directory" -- the first thing a new contributor types. Both now use the flow
from the gershwin-developer README: clone to /Developer, run the scripts from
Library/Scripts/, and build with make install. building.md also contradicted
itself, cloning into ./gershwin-build in Quick start and then using /Developer
under Per-component builds.
linux.md presented one repository as two different tools, telling the reader to
use gershwin-build and then, in the next paragraph, to clone gershwin-developer
for "manual development setup". Collapsed to a single instruction.
Also, while in these files:
* Document the three checkout.sh environment variables. SKIP_REPOS, BRANCH and
PINNED are all in the README but appear nowhere on the docs site, and
SKIP_REPOS is what you want when hacking on a single component.
* Correct the Linux distribution list, which named four; there are package
lists in Library/OSSupport/ for seven (Debian, Devuan, Ubuntu, Arch, Artix,
Manjaro and Void).
* Note that bootstrap.sh and make install run as root, which the building.md
quick start omitted while linux.md used sudo.
* Add the eau-theme build target, which the table was missing.
* Point the Live ISO section at the targets/ directory and ADDING-A-FLAVOR.md
rather than an unqualified "see gershwin-desktop/".
* Replace the vague init-system line with what LoginWindow actually installs a
service for, since it installs none on runit.
Verified: no gershwin-build references remain; every path, make target and
environment variable named here exists in gershwin-developer at main.
Claude-Session: https://claude.ai/code/session_01B3i2SyxJHZ2nBTLAEKGGLx
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The build repository was renamed
gershwin-build→gershwin-developer. The old URL still redirects, so the nine references across five pages look fine — but two of them hand the reader commands that fail.building.mdandrpi.mdboth say:The scripts live in
Library/Scripts/, so that's an immediate "No such file or directory" — on the first command a new contributor types. Both now follow the README's actual flow: clone to/Developer, run the scripts fromLibrary/Scripts/, build withmake install.building.mdalso contradicted itself, cloning into./gershwin-buildunder Quick start and then using/Developerunder Per-component builds.linux.mdpresented one repository as two different tools — usegershwin-build, then in the very next paragraph clonegershwin-developerfor "manual development setup". Now a single instruction.Also, while in these files
checkout.shenvironment variables.SKIP_REPOS,BRANCHandPINNEDare all in the README but appear nowhere on the docs site.SKIP_REPOSis the one you want when hacking on a single component.Library/OSSupport/has package lists for seven — Debian, Devuan, Ubuntu, Arch, Artix, Manjaro and Void.bootstrap.shandmake installrun as root. Thebuilding.mdquick start omitted this whilelinux.mdusedsudo.eau-themebuild target, missing from the table.targets/andADDING-A-FLAVOR.mdinstead of an unqualified "seegershwin-desktop/".Verified
gershwin-buildreferences remain.maketarget and environment variable named here exists ingershwin-developeratmain— checked against a local checkout, not from memory.Library/OSSupport/exactly.sphinx-build -b htmlsucceeds on this branch, and the warning set is byte-identical tomain— 65 both before and after, none introduced. The one new cross-reference, a relative link fromlinux.mdtobuilding.md, resolves.One thing I noticed but did not change
Three pages are missing from the
toctreeinindex.mdand so are not published at all:developer/linux.md,developer/boot.mdanduser/feedback.md. Thetoctreesetsglob: truebut lists entries explicitly, with nodeveloper/*pattern to catch them.Sphinx says so itself, on
mainas well as here:So
linux.md— the page with the worst contradiction — isn't on the site. Fixing that changes site navigation, which felt like a different call from a text correction, so I left it out. Happy to adddeveloper/linuxhere, or open a separate issue for all three, whichever you prefer.https://claude.ai/code/session_01B3i2SyxJHZ2nBTLAEKGGLx