fix(gnome): host-side shell-extension install docs + drop dead settings-schema - #56
Merged
Merged
Conversation
…gs-schema
Close FU-013 and FU-014 from the follow-ups backlog.
FU-014: metadata.json declared settings-schema
`com.strangedaystech.LNXDrive.Indicator` but prefs.js never calls
getSettings() (it only launches the external lnxdrive-preferences app), so
the key was dead and no gschema existed. Remove the key — no gschema needed.
FU-013: the original framing ("extension not in the Meson build") was
inaccurate — shell-extension/meson.build already exists and installs the 7
files correctly (verified: `meson setup -Denable_shell=true` + `meson
install`). The real gap was that no shipped path runs that host-side install
(the Flatpak forces -Denable_shell=false because the extension loads in the
host gnome-shell), so a clean install had no indicator. Document the
host-side Meson install (user and system prefix) in the packaging README.
Verification: meson setup/install clean with the modified metadata; JSON
valid; `node --check` clean on all 5 extension JS files; runtime load on
GNOME Shell 50 already confirmed in AILOG-2026-07-03-002.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
1 participant
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.
Cierra FU-013 y FU-014 del follow-ups backlog (nacidos del fix del indicador, PR #55).
FU-014 —
settings-schemamuerto (real)metadata.jsondeclarabasettings-schema: com.strangedaystech.LNXDrive.Indicator, peroprefs.jsno llama agetSettings()(solo lanza la app externalnxdrive-preferences). La clave estaba sin uso y sin gschema. Fix: eliminar la clave — no se necesita gschema.FU-013 — instalación host-side (con corrección de premisa)
shell-extension/meson.buildya existe (desde 2026-05-28) e instala los 7 archivos.meson setup -Denable_shell=true→ exit 0;meson install→ deposita la extensión en…/gnome-shell/extensions/<uuid>/.La deuda real era más estrecha: ningún flujo shipeado ejecuta ese install host-side (el Flatpak fuerza
-Denable_shell=falseporque la extensión carga en elgnome-shelldel host, fuera del sandbox), así que una instalación limpia no obtenía indicador — de ahí el hand-copy manual de la sesión previa. Fix: documentar la instalación host-side por Meson (prefix de usuario y de sistema) enlnxdrive-packaging/README.md.Nota de proceso
Se declaró un Charter-02 amplio para esto; al ejecutar la primera tarea, la verificación refutó su premisa central (target faltante / build roto). El Charter (nunca commiteado) se abandonó y se degradó a este PR pequeño, alineado con minimum-viable. El registro honesto está en
AILOG-2026-07-03-003.Verificación
meson setup -Denable_shell=true+meson installlimpios con el metadata modificado; los 7 archivos aterrizan.metadata.jsones JSON válido, sinsettings-schema, conshell-versionincluyendo50.node --checklimpio en los 5*.js.straymark validate: 0 errores.Seguimiento
Se registró FU-015: el validador de StrayMark reporta falsos
CHARTER-AILOG-REFpara AILOGs en subdirectorios por componente (deuda del tooling, afecta a Charter-01).🤖 Generated with Claude Code