Define and verify the supported prebuilt artifact matrix

オープン
#103 コメント 4 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
cpp, debian, github-actions, macos, rust

調査の方向性

Read the release workflow in release.yml, the audited artifact matrix documented in #136, and the runtime evidence referenced in the issue. Compare produced binary dependencies and hosted consumer execution across the proposed OS and architecture targets, including glibc and macOS deployment minimums. Done means the supported matrix and installation mappings are agreed, verified, and aligned across recipes, documentation, and CI.

索引モデルが issue の本文から書いたものです。

説明

The published v0.1.9 artifacts contain Linux x64/arm64, Debian 12 variants, and Apple arm64. Current main additionally enables Intel macOS and Windows x64/ARM64 candidate builds with the native acceptance recorded below; this does not change the historical release assets. The versioned recipes repaired in #119 retain their missing-Intel-artifact diagnostic and source-build path until a matching archive is published. PR #50 proposes a glibc 2.28 floor alongside the existing Debian 12 packages and remains author-maintained.

Work

  • Document the audited v0.1.9 artifact matrix, installation mappings, source MSRV and C++17 requirement in #136.
  • Finalize supported OS/architecture and glibc/deployment requirements for each installation path, including the runtime evidence below.
  • Verify the four existing Ubuntu 24.04 / Debian 12 x86_64 / aarch64 Release candidate rows with installed and extracted static/shared data and ownership consumers.
  • Record exercised macOS baselines and distinguish deployment metadata from runtime guarantees; no older macOS minimum is claimed.
  • Retain and verify a current macOS ARM64 Release candidate through the existing install, static/shared consumer and archive path; accepted at source 62fbc0f as recorded below.
  • Replace the retired macOS release runner and verify staged-library architecture through hosted consumer execution, in #141. This accepts arm64 staging and consumer startup, not a minimum-OS runtime guarantee.
  • Adopt glibc 2.28 as the baseline for future generic Linux x86_64/AArch64 packages (user decision, 2026-11-13), retaining Debian 12 variants and PR #50 author ownership.
  • Establish current-core manylinux_2_28 x86_64 build/runtime feasibility and verify the physical lib/ install plus relocated extracted archive with static/shared data and ownership consumers, as recorded below. This is not PR #50 or ARM64 acceptance.
  • Determine Intel macOS prebuilt support and align recipes, documentation, and CI. Accepted candidate build/runtime evidence is recorded below; published recipes remain tied to existing release assets.
  • Coordinate PR #50 ownership and retain useful contributions through an agreed integration path.
  • Verify the current eight candidate rows against produced binary dependencies and real static/shared consumer execution on the recorded OS baselines; this does not accept the proposed manylinux 2.28 row or untested older systems.

Keep the consumer C++ requirement at C++17 unless an accepted feature requires a change. Existing-recipe repair proceeds separately. Parent goal is #99 and related PR is #50.

Accepted runner migration and remaining runtime boundary

PR #141 merged as a730ed5b18f0719626fcb8809a879f3d20ce9360. The accepted head 623f1237d2ceb50fea0402758aeec6f6e2802e28 has ten successful checks. Hosted macOS job 130160620300 built and installed the libraries, ran verify-macos-staging.sh against both static and shared libraries with arm64, and built and started the installed CMake consumer. The retained raw log confirms the expected usage exit path; this job did not open a dataset. The dylib's build metadata reports minos 11.0 and sdk 15.5.

The same log contains linker warnings that some static archive members were built for macOS 15.5 while the consumer linked for 15.0. Therefore, the dylib's minos field alone must not be promoted to a supported runtime floor for the full static/shared distribution. Inspect the final artifacts and execute actual data operations on the claimed runtime baseline before accepting that broader requirement. This was the historical #141 acceptance boundary. Subsequent Intel Release and ARM64 data/ownership evidence is recorded below; no older macOS runtime minimum is claimed. Future release publication, Linux compatibility validation and PR #50 integration remain separate.

Retained evidence: /home/xuanwo/.local/state/codex/lance-c-parity-20261110/macos141-consumer-completed.log (staging at lines 1265-1289, consumer startup at 1548-1567), plus macos141-merged.json. The November 11 reconciliation reused these accepted execution results and refreshed the merged/check states; it did not rerun macOS.

Shared-library release policy

#201 merged as 44c890203b84ccec5adc70d3195e00e7166dd393, completing #163/#164: shared-only stripping, exact public-export guards, removal of unused libssl-dev, and staged Linux runtime-dependency checks. NieR executed the Linux stripped-Release static/shared data-read path; hosted macOS ARM64 executed actual dylib linking/export checks and native consumers. The final hosted integration tree equals the merged tree. These results do not establish a newly published archive, Intel macOS or Windows support, the glibc 2.28 choice, or an older macOS runtime floor. Later platform acceptance is recorded below; #201 alone did not establish those broader results.

Windows x64 build-path acceptance

#206 merged as a978709b9d23247895cadb648868195f36f08ed4. The exact-candidate Windows Server 2022 x64 build/install, PE/export/dependency inspection, and installed static/shared dataset consumers passed; #174 records the source, toolchain, runtime baseline and candidate artifact identity. This accepts the Windows build path on that exercised baseline, not older Windows or a published release. #174 now also records successful Windows 11 Enterprise 10.0.26200 ARM64 native staging and installed static/shared consumer execution on the #212 test-merge. #212 merged as 3794c161bd770ed9fa31b389d4e7da1fc09030a7, retaining the exercised platform inputs; this result does not establish older Windows, self-contained VC Runtime deployment (#215), or a published release. Intel macOS #208 native Release/staging/consumer acceptance is recorded below. The historical v0.1.9 matrix, glibc 2.28 decision and #50 ownership boundary are unchanged.

Windows distribution dependency follow-up

#214 is complete through #216, and #215 is now complete through #217 (62fbc0fd69d66b184643e47ce93f7f3a6525598b). The accepted combined x64/ARM64 packages have exactly 878 DLL exports and matching import-library symbols, static CRT metadata, 16 distinct OS/API-set imports and no delay imports. Full native static/shared ownership/data consumers and loaded-module runtime guards passed on Windows Server 2022 x64 and Windows 11 ARM64. Static archive consumers require Release /MT; prebuilt CRT declaration is explicit. #174 records the exact candidate identities and limits. This is candidate/native distribution acceptance, not a new release or downstream Go adoption. The four existing Linux rows are accepted below; author-maintained manylinux 2.28 work remains separate. Unclaimed older macOS versions are an evidence limit, not a new delivery prerequisite.

Intel macOS candidate acceptance

#208 merged as f9e6f322eac3584efe39e4d968abe565aa89d89e. Head 604938407b748957f22af81d6c5f28e1bf672319, hosted test-merge cae4216b8f6fa755aa05498f507bf8f8062205bd, and the resulting main commit share tree 551d11bdc03efa159719220c6b42dc0a7e3dc186. All ten checks passed. Native Intel job 130915319083 ran on macOS 15.7.9 with Rust 1.99.1, built direct Cargo and Corrosion Release libraries, verified exactly 878 public exports, x86_64 architecture, install name and OS dependency policy, and packaged the candidate. Installed static and shared consumers each read the 512-row/version-2 historical dataset and passed create/reopen/scan, Arrow release counts, last-error ownership and clone-after-close tests.

The downloaded candidate ZIP matches SHA-256 fddf8e31322d5e3de4ca5fd28ca74c1ffec3fca65d6d2f2f7fe892195d7abc94; its tarball matches both supplied checksums (SHA-256 2ba03fa1d859a64d23f2322c67d515cf58459a380b98295d2e809fd4700c8a24). Packaged headers match source and library hashes match staging. Raw logs, API snapshots and verified member hashes are retained under /home/xuanwo/.local/state/codex/lance-c-maintenance-20261111/pr208-final-native-evidence/.

Current-main reconfirmation: Intel job 131048950519 passed at 62fbc0fd69d66b184643e47ce93f7f3a6525598b on macOS 15.7.9 with Rust 1.99.1. Direct Cargo and Corrosion Release paths, exact 878 exports, staged architecture/install-name/dependency guards, and both installed data/ownership consumers passed. The retained candidate ZIP SHA-256 is 1aaa22a1a7b7e9ff6cc808a6d16a766ce42c38dbd60ee788cf5af962f30e4f08; the enclosed tarball SHA-256 is d3f635d809837d2806b0406567eab5817f6cf9498e8aae3320d241826bb946e4. ZIP size/digest, tarball SHA-256/SHA-512, exact source headers and both archived library hashes were independently checked against the staged identity records. This additional candidate has no new full static-member deployment-target audit; the member counts below identify the earlier #208 archive. It is not a published release.

This accepts Intel candidate production and execution on the tested macOS baseline. It does not establish runtime on macOS 11 merely because minos is 11.0, or claim a tag/release. v0.1.9 still has its historical five assets, and Intel recipes continue source mode until a matching published archive exists. Current ARM64 macOS Release acceptance is now recorded below. The glibc 2.28 requirement and integration of author-maintained PR #50 keep this issue open; the existing Linux matrix is accepted below. Current macOS runtime evidence is scoped below; a numeric older-system minimum is not being introduced.

Contributor coordination (2026-11-12 UTC)

PR #50 remains with its author, who confirmed plans to address the review comments by the weekend. Its current conflicts still require integration and acceptance; the response is not a transfer of authorship or branch ownership. Verification of the existing Ubuntu 24.04 and Debian 12 Linux package paths proceeds independently and does not replace the manylinux 2.28 contribution.

macOS runtime and deployment-target reconciliation (2026-11-12 UTC)

Documentation clarification merged in #219 as 69c2d0358194c70d1305dea81b5854cea867ef44. The README distinguishes the historical published archive, Intel Release candidate and ARM64 debug evidence, and explains the environment propagation through Corrosion. All ten checks passed; the merged tree matches the reviewed candidate. The documentation change alone did not establish ARM64 Release package acceptance; the later native Release result is recorded below.

The current README and package recipes specify macOS architectures without promising a numeric minimum OS version. Binary deployment targets and actual execution are separate evidence:

Distribution / source Mach-O metadata Retained runtime acceptance
Published v0.1.9 ARM64 archive Dylib minos 11.0; 416 of 3,298 static members declare minos 14.5, the archive maximum No retained macOS execution evidence for this published archive
#208 Intel Release candidate 6049384 Dylib minos 11.0; all 3,341 static members declare at most 11.0 macOS 15.7.9: installed static/shared historical-data and ownership consumers pass; candidate identity is recorded above
#217 ARM64 current-source 335dbac Dylib minos 11.0; complete static-member metadata unavailable because runner libraries were not retained macOS 15.8.2: installed debug static/shared libraries pass historical-data and ownership consumers; this is not ARM64 Release archive acceptance

macOS ARM64 job 131011816224 records rows: 512, version: 2 and acceptance: PASS for both linkages. Its installed static library SHA-256 is 435e7fea5b8a7ea9b774cc83f64d6f9b033b9777cc50a97d19efc059e03bf5df; its dylib SHA-256 is 59d7d75c06c19d652a4dd2e80b926ba4c01b22c996ad8a102806c50a157d7ce6. These hashes identify the exercised debug files, not a retained Release package.

The published v0.1.9 archive SHA-256 is dbbf6b62d091c134643e4ce84eda868fe72c3dcb43414ecacce83f60756b6b31. Its mixed member targets prevent deriving a whole-package macOS 11 guarantee from the dylib alone; they do not prove that every static consumer fails below 14.5. The old #141 warning similarly describes mismatched build targets, not a demonstrated failure on its exercised 15.8.2 host.

Current CI/release jobs export MACOSX_DEPLOYMENT_TARGET=11.0 to Cargo and native dependency build scripts. With pinned Corrosion 0.5.1, setting only CMAKE_OSX_DEPLOYMENT_TARGET does not provide that Cargo environment. The audited public contracts do not require a new build change or a blanket old-OS test matrix. A future numeric minimum would need actual consumer execution on that chosen architecture/linkage/OS; it is not established here. Documentation reconciliation proceeds independently. The current ARM64 Release package evidence is now accepted below; it adds no older-OS support promise. The existing Linux matrix is accepted below; author-owned manylinux work remains open.

Current Linux candidate matrix acceptance (2026-11-12 UTC)

All four existing Linux release rows passed Release build, install, shared-only stripping, exact header-derived exports, ELF architecture/dependency checks, and real installed and archive-extracted static/shared consumers. Each row produced four rows: 512, version: 2 results and four acceptance: PASS results across those two prefixes and two linkages. Ownership coverage includes create/reopen/scan, Arrow release counts, error-string ownership and clone-after-close.

Exercised runtime Architecture Highest referenced GLIBC version Candidate archive SHA-256
Ubuntu 24.04.5 / glibc 2.39 x86_64 (native) GLIBC_2.39 a011f32d345738593b7393bfe1b48616d8d353854aaa2d823daf7eb9ea0f74c0
Debian 12.15 container / glibc 2.36 x86_64 (native) GLIBC_2.35 4b67988e9486dcea882ff81930f075e4c11457cd2509478beed8c65394534051
Ubuntu 24.04.5 / glibc 2.39 aarch64 (native) GLIBC_2.39 4c4a127f98f3ad46f1fd4709bec02b013aab07ecb9bc77e533714d48d4b14a81
Debian 12.15 container / glibc 2.36 aarch64 (native) GLIBC_2.35 504c4672a334177c64ff9e05054c81eb97dabac5c02a029eeaf44a53cf4897ad

Source was 009d33f85cb7ac087d0c25add1161dd003ba47c8, tree 4338cecd7b5fc473bd32d7a8d2dcb921e484b708, built with Rust 1.94.0 and the unchanged Lance 14.0.2 pin. All four archives have exactly 878 public exports matching the installed header, no extra dynamic exports, and no GLIBCXX/CXXABI references. Static libraries were unchanged by the shared-library strip step. Downloaded archive SHA-256/SHA-512, source-header hashes, installed/extracted file manifests and path sets were checked; raw logs confirm actual data and ownership execution, not usage-only startup.

The x86_64 Ubuntu and Debian-container runs were native Linux executions; they were not hosted x64 runner-image acceptance. The native ARM64 workflow exercised ubuntu-24.04-arm and its Debian 12 container without QEMU. Debian used image digest sha256:268fb24c39bca92d326dd83ea3abebe4a3f7751c804ffef23bb6d857dd343ff8. The temporary validation branch adds only three evidence-driver/workflow files; product source, release workflow and dependency pin were not changed for these measurements.

A source comparison against current main@62fbc0f confirms: Rust source, headers, manifest/lockfile, build script and the Linux verifier are identical. #218 changes ordinary CI download setup; #217 changes Windows CRT/consumer behavior and adds inert LanceC_STATIC_CRT=OFF package metadata on Linux. The Linux release row/build behavior is unchanged. This supports reuse of the measured candidate evidence, not a claim that the final main tree was executed here.

These are retained candidates, not a published release. Production release jobs select stable; this acceptance specifically exercised Rust 1.94.0. GLIBC symbol maxima describe loader requirements, while runtime acceptance is limited to the OS/container versions above. It does not establish glibc 2.28/manylinux compatibility or finish PR #50. Current ARM64 macOS Release candidate acceptance is now recorded below; author-maintained manylinux integration remains open.

Current-main Windows package reconfirmation

At 62fbc0fd69d66b184643e47ce93f7f3a6525598b, main CI 43176014755 completed all nine jobs successfully. Both Windows architectures passed Rust 1.94.0 Release build/install, exact 878-symbol DLL/import-library checks, static CRT and dependency/module guards, and installed static/shared data and ownership consumers. Downloaded ZIP sizes/digests, all member hashes, source headers and static-CRT package metadata were verified; #174 records the identities and exercised OS limits. These remain candidates, not published release assets. The separate current macOS ARM64 Release acceptance is now recorded below; author-maintained manylinux work remains pending.

Current macOS ARM64 Release candidate acceptance (2026-11-12 UTC)

Native ARM64 job 131057410886 passed CMake Release build/install, shared-only strip, Corrosion linker selection, exact 878-symbol exports, architecture/install-name/dependency checks and installed static/shared data and ownership consumers. The host was macOS 15.8.2 ARM64, Xcode 16.4 / SDK 15.5, with Rust/Cargo 1.94.0. Each linkage read the historical 512-row/version-2 dataset and completed create/reopen/scan, Arrow release counts, last-error ownership and clone-after-close acceptance; a separate shared-loader probe also read the dataset. Usage-only invocations are not counted as runtime acceptance.

Product source is 62fbc0fd69d66b184643e47ce93f7f3a6525598b, tree d994d6abbb46024f5411db42e8f4a5ede59225f4. The validation commit adds evidence collection and optional consumer-log retention without changing product inputs. Current main 69c2d03 differs from that product source only in README, so this result remains applicable to the current package path.

The retained static archive has 3,855 Mach-O members, all ARM64 with minos 11.0; an independent scan reproduced their identities and metadata. The static archive is unchanged by stripping. Dylib SHA-256 is fc77668d47e6df3a6745dd039dc3fbd1d092ec762528d473f70b002ffe52478d; static library SHA-256 is 045ab786f1225aeb9bb619aee32360e6bfdfb2e3a5429305d31a35c9d8172d11.

The unpublished candidate archive SHA-256 is af703a0f4d31af671152c8c8394e9866450f47a895a65ac8edf4e54102939bcc. Both downloaded artifact ZIPs match live API digests/sizes; inner archive checksums, packaged/source headers and installed/extracted file manifests match. Raw logs, downloaded binaries, member metadata and checksums are retained. This closes the concrete ARM64 Release archive evidence gap, and all eight existing candidate rows now have scoped native execution evidence.

Only macOS 15.8.2 runtime is established by this ARM64 execution. minos 11.0 remains build metadata, not a macOS 11 guarantee. This is an unpublished candidate: historical v0.1.9 receives no new runtime promise, and no tag, release or versioned recipe update is implied. The manylinux/glibc 2.28 decision and PR #50 integration remain independent unfinished work.

The README now records this accepted ARM64 Release candidate through #220, merged as 6d805a834c738d71cb67ba329e1e3c1194509e78. The merged tree matches the independently reviewed one-row documentation change; all ten checks passed. This replaces the superseded DEBUG-only row without changing the historical v0.1.9 or Intel evidence, publishing a package, or establishing an older macOS runtime floor.

manylinux_2_28 x86_64 feasibility (2026-11-12 UTC)

Unchanged product source 69c2d0358194c70d1305dea81b5854cea867ef44, Lance 14.0.2 pin 40f15ed1b71b66950961b175829fdf17a763f108, built and ran with Rust 1.94.0 and Clang 20.1.8 in native x86_64 AlmaLinux 8.10 / glibc 2.28. The manylinux image digest was sha256:9555ba6c479fa69a2aa80ad1dc57154a60d562b19df159361d9379a02beb1e36. The validation driver is separate from product changes.

Release build/install succeeded. The stripped shared library has exactly 878 header-matching exports, no additional exports, a maximum required GLIBC version of 2.28, and only the recorded system/libgcc dependencies. Both installed C++17 static/shared consumers read 512 rows at version 2 and passed create/reopen/scan, Arrow release counts, last-error ownership and clone-after-source-close checks in that container. Static SHA-256: d6760773b7c6f0055590f811c4a53f61892da1d2142ca1a4e894ef195def3aa1; stripped shared SHA-256: fa74d0debd951e11c70ce9a3c9c1070a2c8b280a99bbb7f0a726778dd695ca7c. Raw commands, statuses, source identities, logs and 124 evidence-file hashes were retained and checked.

The November 12 experiment used a symlink compatibility view because this image defaults to CMAKE_INSTALL_LIBDIR=lib64 while the existing archive scripts expect lib. The November 13 follow-up below closes the physical-layout and extracted-archive evidence gaps with explicit -DCMAKE_INSTALL_LIBDIR=lib. The author-maintained PR #50 workflow and a decision to adopt this baseline remain separate. C++17 sufficed; no C++20 requirement was demonstrated.

This does not accept ARM64 manylinux, an extracted release archive, every glibc 2.28 distribution, or PR #50's workflow. The protoc asset digest was recorded and rechecked but was not independently authenticated against a vendor checksum. PR #50 remains author-maintained; its current release-matrix findings and ownership coordination are separate. Existing Debian 12 packages remain unchanged. No tag or release was produced.

manylinux physical install and relocated archive acceptance (2026-11-13 UTC)

Product 9d7fda2c9513a468aafb762c16e1aa0e6dc56309 (tree 4e0065a40020590d6f3d6fd4bc6f36b0e65b88f5) passed the explicit -DCMAKE_INSTALL_LIBDIR=lib Release configure/build/install on the same pinned native x86_64 AlmaLinux 8.10 / glibc 2.28 image. Rust was 1.94.0, Clang 20.1.8 and CMake 4.4.4. The installed prefix physically contains lib/, no lib64 and no symlinks. CMake and pkg-config metadata resolve within the installed or extracted prefix. The validation driver is a direct child of that product commit and changes no product files.

The candidate archive was extracted into an independent prefix, then the original install prefix was renamed and made unavailable before fresh find_package(LanceC) static/shared consumers were configured, linked and run. Both linkages read the historical 512-row/version-2 dataset and passed create/reopen/scan, Arrow release counts 2/1/1, last-error ownership and clone-after-source-close checks. The static consumer has no liblance_c.so dependency; the shared consumer resolves the extracted .so. A pkg-config consumer also read the dataset from the extracted package. The installed and extracted libraries each match all 878 current public exports; all 3,787 static archive members are x86_64. The shared library and both static data/ownership consumers require GLIBC no newer than 2.28, and the library's DT_NEEDED remains within the recorded system/libgcc set.

Candidate lance-c-v0.1.9-x86_64-unknown-linux-gnu.tar.xz: 197,293,796 bytes, SHA-256 0130ede10d16dccb0fb35d3ac5fdd3ae6e00fabc29b3056fe727d3c3d7eebed1. Raw evidence and candidate payload remain on NieR at /home/xuanwo/.local/state/codex/lance-c-maintenance-20261113/manylinux103-lib-acceptance/; the coordinator retained and inspected the actual configure, installed/extracted consumer logs, link/dependency records, source identity, archive hash and final status. Initial verifier failures remain preserved; the final resumed body exits 0 with ACCEPTED, reusing the already-built explicit-lib installation. An older outer-wrapper failure record is not presented as the final result.

This accepts that unpublished x86_64 candidate in the pinned container, not ARM64, every glibc 2.28 distribution, PR #50, an official manylinux release, or a change to historical v0.1.9 assets. Existing Debian 12 packages remain unchanged. Install/package metadata contains no original-prefix or build-path references; compiler-generated absolute source strings remain in the binaries, so zero embedded build paths is not claimed. Protoc v25.3 was fetched over HTTPS with a locally pinned digest; no vendor checksum asset was available. The glibc-support decision and PR #50 ownership/integration remain open.

Native manylinux ARM64 candidate acceptance (2026-11-13)

The same product source 9d7fda2c9513a468aafb762c16e1aa0e6dc56309 also passed native AArch64 build, physical lib/ installation and extracted-package acceptance in run 43396989763 / job 131790218176. The validation-only source used an ubuntu-24.04-arm host and quay.io/pypa/manylinux_2_28_aarch64@sha256:cb37f0d66c8a75abb93cf6085cad1f1427cd7208f0c0fc48359bb1eea9924f21 (AlmaLinux 8.10, glibc 2.28), Rust 1.94.0 and Clang 20.1.8. Product code, dependency pin and release workflow were unchanged.

Release build/install, shared-only strip, exact 878 public exports, AArch64 ELF and dependency checks passed; the shared library requires no GLIBC version newer than 2.28. All 3,868 static archive members are AArch64 and the archive is byte-identical before/after shared stripping. Installed and freshly extracted static/shared consumers read 512 rows / version 2 and passed create/reopen/scan, Arrow release, error-string ownership and clone lifetime checks. The original prefix was unavailable before extracted consumers were built and executed; the shared loader initialized the extracted library and static consumers did not depend on it. Installed/extracted file manifests and path sets match.

Candidate archive: 183,360,944 bytes, SHA-256 e1f1f5447fe378653d5d536fc0a2f9917c0faf4f1593d912713aa88007bd4538. The coordinator verified all 129 retained evidence-manifest entries and the 32 successful driver stages, and read the consumer and loader logs. The archived raw summary has four convenience-field formatting/count errors; corrected values are derived separately from primary stat/member records, without changing the original evidence or claiming a second build. Evidence is retained under manylinux103-arm64-feasibility/ in the maintenance record.

This closes the ARM64 feasibility gap alongside the accepted x86_64 experiment, within the two recorded glibc 2.28 containers. The candidate filename contains the workspace version v0.1.9; it is not a published v0.1.9 asset. It does not accept PR #50, establish all-distribution compatibility, change the Linux support policy or publish a release. Author ownership and release-workflow integration remain separate; this issue remains open.

Adopted Linux baseline and integration ownership (2026-11-13)

The user explicitly adopted glibc 2.28 for future generic Linux x86_64 and AArch64 official packages, using the accepted native manylinux_2_28 evidence above. Keep the physical lib/ layout, existing Debian 12 variants and C++17 consumer contract. This lowers the selected loader baseline; runtime evidence remains scoped to the exercised containers and does not promise every distribution.

The feasibility and policy decisions are now complete. PR #50 remains author-maintained: integrate and accept the author's actual updated workflow, conflicts and package/consumer paths before closing this issue. No author handoff is inferred. Reuse the accepted architecture experiments and validate only changed integration inputs. Historical release assets and downstream Go native modules are unchanged; this decision does not publish a release or accept PR #50.

Policy and installation documentation adopted (2026-11-13)

PR #225 merged as c9cffeab0df0267d139cae6c3110e42750ac13ff after all 10 checks passed on 094c818fd64a8300c95fb40beaf654b6cb793982. README and the vcpkg/Conan installation docs now separate published v0.1.9 archives from the adopted future glibc 2.28 policy and scoped candidate execution. Existing Debian 12 variants remain distinct. The Linux dependency-install timeout was recovered with one successful Linux-only retry; no platform experiments were repeated.

This completes the documentation portion only. Author aheev still owns #50 workflow integration; the existing author request and weekend commitment remain in force, with the next recheck on 2026-11-16 at 09:18 UTC. This issue stays open until the actual packaging integration is accepted. No new archive, recipe payload, Go module, or release was published.

主要言語
Rust
スター
8
フォーク
17
平均マージ
1時間 14分
マージ済み PR(30日)
89

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

lance-format/lance-c のほかの issue

lance-format/lance-c の issue をすべて見る

似ている issue

Rust の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。