docs: cover the Windows target and lgpm --platform - #79
Merged
Conversation
The guide had no Windows content at all, and `lgpm` grew a `--platform` flag (logos-package-manager 1ac7963) that nothing documented. Three additions, all places the guide already made a claim that is now incomplete or wrong for Windows: * The variant-naming table gains `x86_64-windows`, with a note that the spelling is `windows-x86_64` and — unlike Linux, which accepts both `linux-x86_64` and `linux-amd64` — it has NO alias, so a package labelled `windows-amd64` simply will not install. * 5.1 documents `--platform`, including why the default refusal exists. lgpm derives the variant from the machine it runs on and fail-closes otherwise; that refusal is the protection against installing a package built for one platform onto another, so the opt-out is explicit and never inferred, applies to install/list/info alike, and prints to stderr when active. With an explicit warning NOT to use it for a dev/portable mismatch: forcing that installs a package the runtime cannot load, trading a clear install-time error for a confusing load-time one. * "Cross-platform builds" said to build on each target platform separately. That cannot be done for Windows — there is no Nix daemon for Windows, so it is cross-built from Linux (or from WSL2, which is Linux) and copied across. Branched from master rather than the checked-out fix/ui-doctest-launch-timeout so this carries none of that branch's work. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
📊 Tutorial execution reportRendered tutorial alongside the commands actually run and their output (updated each run, commit Pages can take a minute to update after the run finishes. |
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.
Documentation for the Windows target and the
lgpm --platformflag that cross-installation needs.Context
L1 of a 30-PR Windows chain. Docs only — no flake, no dependents, so it can land whenever.
What it covers
x86_64-windowsand what the pseudo-system means (a cross derivation'ssystemattr is its build platform, sonix build .#packages.x86_64-windows.…realises on anx86_64-linuxmachine).lgpm install --platform windows-x86_64, which exists becauselgpmotherwise computes the variant of the machine it is running on — correct, and exactly why cross-installation from the Linux builder was not expressible before.Caveat for the reviewer
Per the repo's tutorial-sync rule, docs here must track the code they describe. The commands documented reflect the branches in this chain, several of which are not merged yet — so some examples will not run against
masteruntil the chain lands. Worth deciding whether that is acceptable for a docs-first merge or whether this should move to the end of the order.