L. C. Hsieh created SPARK-61432:
-----------------------------------

             Summary: Add LICENSE-binary and NOTICE-binary for the convenience 
binaries
                 Key: SPARK-61432
                 URL: https://issues.apache.org/jira/browse/SPARK-61432
             Project: Spark
          Issue Type: Sub-task
          Components: Connect
    Affects Versions: connect-gateway-0.1.0
            Reporter: L. C. Hsieh
            Assignee: L. C. Hsieh


The first release will ship convenience binaries (the Docker image) in addition
to the source release. The gateway binary statically links its Rust
dependencies, so the binary distribution needs a LICENSE and NOTICE that cover
the third-party code compiled into it.

Census of the crates linked into the gateway binary on Linux x86_64 (cargo tree
-p gateway -e normal,no-proc-macro --target x86_64-unknown-linux-gnu):

- 239 third-party crates, all Category A.
- Two licenses not listed on https://www.apache.org/legal/resolved.html have
  explicit rulings: CDLA-Permissive-2.0 (webpki-roots) is Category A per
  LEGAL-732, and Apache-2.0 WITH LLVM-exception (build/test only, not in the
  binary) is treated as Apache-2.0 per LEGAL-494.
- Choosing Apache-2.0 wherever a crate offers it, 158 crates are Apache-2.0 and
  81 need their own license text: MIT, Unicode-3.0, BSD-3-Clause, ISC, Zlib,
  CDLA-Permissive-2.0, BSL-1.0, and ring (Apache-2.0 AND ISC).
- No linked crate ships a NOTICE file, so NOTICE-binary carries no third-party
  notices.

The OS packages in the distroless base image are the "system" layer and stay
out of LICENSE-binary (LEGAL-437, LEGAL-695).

This adds LICENSE-binary, NOTICE-binary and a licenses-binary/ directory with
the license texts, and puts them in the Docker image. It also adds a dev script
that regenerates the crate list from cargo tree, so the files can be checked
against Cargo.lock before each release.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

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

Reply via email to