Skip to content

the three board and freestanding packages adopt [xlings.workspace] - #332

Merged
Sunrisepeak merged 1 commit into
mainfrom
feat/xlings-workspace-migration
Sep 3, 2026
Merged

the three board and freestanding packages adopt [xlings.workspace]#332
Sunrisepeak merged 1 commit into
mainfrom
feat/xlings-workspace-migration

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

riscv-virt-rt 0.6.1, aarch64-virt-rt 0.1.1, std-freestanding 0.5.2.

mcpp 2026.9.3.2 makes [xlings.workspace] the table an author writes, and a namespaced package is written "<namespace>:<name>" = "<version>". Each package now declares its environment that way.

Both spellings are kept, on purpose

An engine that knows the table collapses them, because they agree; one that predates it reads deps and behaves exactly as before. Dropping the older line would be a silent regression there: such an engine parses [xlings.workspace] perfectly well and provisions nothing from it, so these packages' own build.mcpp would find no emulator through mcpp::xpkg_dir and would configure no runner. The line goes once no supported engine needs it.

Verification

Package Version sha256
riscv-virt-rt 0.6.1 6703365a…
aarch64-virt-rt 0.1.1 da297279…
std-freestanding 0.5.2 c919229d…

Every hash was computed from the GitHub tarball and then verified against the CN mirror by re-downloading it — the two hosts are known to serve the same bytes rather than assumed to. Each descriptor parses under mcpp xpkg parse on 2026.9.3.2.

riscv-virt-rt 0.6.1, aarch64-virt-rt 0.1.1, std-freestanding 0.5.2.

mcpp 2026.9.3.2 makes [xlings.workspace] the table an author writes, and a
namespaced package is written "<namespace>:<name>" = "<version>". Each package
now declares its environment that way and keeps the older [xlings] deps line
beside it: an engine that knows the table collapses the two, and one that
predates it reads deps and behaves as before. Dropping the older line would be
a silent regression there — such an engine parses the table and provisions
nothing from it, so these packages' own build.mcpp would find no emulator and
configure no runner.

Every sha256 was computed from the GitHub tarball and then verified against the
CN mirror by re-downloading it, so the two hosts are known to serve the same
bytes rather than assumed to.
@Sunrisepeak
Sunrisepeak merged commit 60fca19 into main Sep 3, 2026
8 checks passed
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