abnobdoss commented on issue #13950: URL: https://github.com/apache/skywalking/issues/13950#issuecomment-5234688846
@kezhenxu94 Thanks, this is helpful! I hadn't looked at the `--summary`/`--output` flags before, and I can see cases where generating the files at release time would remove the drift problem at the source. Unfortunately I'm not sure whether this would be accepted for Rust projects under ASF governance. `cargo publish` packages each crate straight from the working tree (and refuses a dirty tree without `--allow-dirty`), so anything shipping to crates.io needs the per-crate LICENSE/NOTICE committed in-tree, otherwise the published crates wouldn't match the voted source. This would also be true for the source tarball when it's cut with `git archive` from the release tag (as iceberg-rust does): the artifact has to match the audited tree. Do you know of any Rust projects under ASF or similar governance that publish to crates.io and generate LICENSE/NOTICE at package time? If this is the direction you'd recommend for eyes users, a precedent like that would make it easier to point to as the answer whenever this kind of drift comes up. -- 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]
