| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
The 0.6.0 manifest states a capability the previous release did not, and the index serves published tarballs rather than branches. Without this entry a consumer resolving openkal by version gets content in which the package declares no layer, and the engine resolves its target side to the compiler payload instead of to the graph. CN mirror verified byte-identical to the GitHub archive before this entry was written. Claude-Session: https://claude.ai/code/session_01Q4ucduLuSsETHYJ1RkGVVD
Every one of these manifests states a capability the previous release did not. mcpp resolves the target side per layer after the dependency graph is known and reads which layer a package fills from its capabilities; the index serves published tarballs rather than branches, so without these entries a consumer resolving by version gets content in which no package declares a layer and the engine resolves the target side to the compiler payload. openkal-llvm-runtime had no descriptor at all. It is the entry point for a program that reaches several machines from one source -- it names the C library, which selects the platform implementation, which names the specification -- so its absence meant that path was reachable only through a git reference, which is not a supported way to depend on a package. Every CN mirror object was fetched and compared against the GitHub archive before its entry was written here; all nine are byte-identical. Claude-Session: https://claude.ai/code/session_01Q4ucduLuSsETHYJ1RkGVVD
| Back | FazBrowse Home | New Git URL |
Nine packages released as part of the target-side resolution closure (mcpp-community/mcpp#486).
Every CN mirror object was fetched and compared against the GitHub archive before its entry was written; all nine are byte-identical.