kevinjqliu opened a new pull request, #3493:
URL: https://github.com/apache/iceberg-rust/pull/3493

   ## Which issue does this PR close?
   
   - Part of #3239.
   
   ## What changes are included in this PR?
   
   The wheels statically link ~270 Rust crates but ship no third-party 
attribution. This adds it with `cargo-about`, as a smaller alternative to #3380.
   
   - `release_python.yml`: sdist and wheel jobs build `bindings/python/LICENSE` 
as root `LICENSE` + `cargo about` output (`about.toml`, `about.hbs`).
   - `bindings/python/LICENSE` is now a placeholder in the repo, `NOTICE` a 
real file. Both used to be symlinks.
   - `bindings/python/NOTICE` has the Arrow, Avro and moka notices. This is 
hand-maintained, so it can drift when dependencies change.
   
   Not covered yet: `zstd-sys` (vendored zstd C code, BSD-3) and 
`brotli-decompressor` (MIT half of BSD-3 AND MIT) need clarifications, which 
I'm leaving for the planned `cargo-about` clarify work. Proc-macro crates are 
also over-listed (~49 permissive ones, no cargo-about filter).
   
   ## Are these changes tested?
   
   Ran the exact `cargo about generate` command locally with a clean 
`CARGO_HOME`, built a wheel and sdist, and checked 
`dist-info/licenses/{LICENSE,NOTICE}`. `make check-license-notice` passes. The 
release workflow itself hasn't run (Windows `>>` redirect, `taiki-e` install of 
cargo-about), so please check the sdist and wheels from the RC.
   
   ## AI Disclosure
   
   Written with Copilot (Claude). Please focus on whether the policy reading is 
right (Category A/B list in `about.toml`, NOTICE handling) and the known gaps 
above. Not reviewed by ASF legal.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to