Repository navigation
The openkal 0.25 family: openkal 0.25.0, openkal-kit 0.3.1, linux 0.26.0, macos 0.23.0, windows 0.21.0, emscripten 0.14.0, opensbi 0.9.0 - #744
Merged
Conversation
Sunrisepeak
marked this pull request as draft
November 9, 2026 19:27
Member
Author
|
Held as a draft: the candidate gate builds tests/examples/openkal with the candidate, and that consumer also names openkal-linux 0.25.0, which requires openkal 0.24.0 exactly, so the specification cannot be proven alone. This change becomes the family's one index change: the implementations (openkal-linux 0.26.0, openkal-macos 0.23.0, openkal-windows 0.21.0, openkal-emscripten 0.14.0, openkal-opensbi 0.9.0) and the example consumer move to the 0.25 family here, and openkal-kit gets a direct consumer in the same example. |
…equests to end counted
…emscripten 0.14.0, opensbi 0.9.0; the examples moved to it, and openkal-kit has a consumer tests/examples/openkal names the family and observes a second name for a file where the volume states it. tests/examples/openkal-kit consumes the kit through the index, so the candidate gate has a member that names it.
Sunrisepeak
force-pushed
the
openkal-0.25.0
branch
from
November 9, 2026 20:57
6fc3162 to
02e1625
Compare
Sunrisepeak
marked this pull request as ready for review
November 9, 2026 20:57
…d is a workspace member kit 0.3.0 wrote at most three digits of a port (8080 as 080); 0.3.1 writes them all. The openkal-kit member formats 8080, so it exercises the fix, and the workspace root names it among its members.
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 openkal 0.25 family, in one change (as mcpp-index#716 did for 0.24):
Each entry is in the linux, macosx and windows blocks, with the GLOBAL (GitHub tag archive) and CN (gitcode.com/mcpp-res) URLs. The source PRs: mcpplibs/openkal#64, openkal-linux#52, openkal-macos#46, openkal-windows#46, openkal-emscripten#17, openkal-opensbi#22, and openkal#65 for kit 0.3.1. Each was green on its original suite and on its mtest suite before merge.
What 0.25 adds:
kal_fs_hard_link, answered per volume byKAL_FS_PROP_HARD_LINKS(clause 11 entry 59). The stop word counts each request to end and skips zero when it wraps (entry 60). openkal-emscripten statesrequires = ["mcpp:c-abi"].Consumers:
tests/examples/openkalnames the 0.25 family and adds an observation: where the volume states it, a second name for a file reads as the first, and a taken name is refused.tests/examples/openkal-kitis new and consumes the kit through the index. It formats port 8080, which kit 0.3.0 wrote as "080"; 0.3.1 (openkal-kit 0.3.1: a port is formatted with all its digits openkal#65) writes every digit, and it replaces 0.3.0 here. The member is listed in the rootmcpp.tomlworkspace members. The scan previously failed with "no candidate consumer: mcpplibs:openkal-kit". Kit 0.2.0 was indexed by feat(openkal): the 0.9.0 ecosystem — nine packages, one change #275, before the scan existed, and kit's archive URL differs from the specification's, so the same-archive sibling rule does not apply.Both members pass locally with mcpp 2026.11.9.1 against this branch's index (openkal 0.25.0 and openkal-linux 0.26.0 resolved from it).