commit | 1896ac84f9fe1aae2e74fdea26ff0fe4ff7d9d4e | [log] [tgz] |
---|---|---|
author | Abhishek Pandit-Subedi <abhishekpandit@google.com> | Tue Dec 14 21:09:04 2021 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Dec 17 01:02:47 2021 |
tree | a01d0e99e987ee882ac5f2f322a96b4eabf64c2e | |
parent | 3cd0435541174f60037672ae5355dba9fa3fcc13 [diff] |
Upgrade grpcio and grpcio-sys to 0.9 Updating grpcio to 0.9 results in the following changes: - boringssl-src[0.2.0 -> 0.3.0]: Unused since we use openssl. - grpcio[0.8.2 -> 0.9.1] - grpcio-sys[0.8.1 -> 0.9.1] - libz-sys[1.1.2 -> 1.1.3] BUG=b:210706048 TEST=emerge-zork-floss floss succeeds Cq-Depend: chromium:3335396 Change-Id: Ib2c735b3638c6a2f149947d9c4970bdbd071e8bd Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/rust_crates/+/3339791 Tested-by: Abhishek Pandit-Subedi <abhishekpandit@google.com> Reviewed-by: Sonny Sasaka <sonnysasaka@chromium.org> Commit-Queue: Abhishek Pandit-Subedi <abhishekpandit@google.com>
This repository contains vendored Rust libraries for the system bluetooth project. It is currently in an experimental state where we are simply running cargo vendor
to store all our dependencies.
Please reach out to the individuals listed in the OWNERS file if you'd like to know more about this repo.
In order to update any package, follow these steps:
Cargo.toml
to add, remove or upgrade packages.python vendor.py
cargo vendor
first, which updates Cargo.lock
and puts downloaded crates into the vendor
directorypatches
directory. It also regenerates checksums for packages that were modified.--license-map=<filename>
is given, it will dump a json file which is a dictionary with the crate names as keys and another dictionary with the license
and license_file
as keys.cargo vendor
seems to also pick up dependencies for unused configs (i.e. windows). You will need to make sure these packages are stripped by cargo vendor
.vendor.py
script with the new license and also update net-wireless/floss-9999.ebuild
with the new license.When it is necessary to patch a package due to incompatibility, you can create a patch targetting the specific package and store it in patches/${package_name}/
with the extension .patch
. The patch will be applied when you run vendor.py
.
Updates to this repo will be captured by CQ (currently zork-floss-cq). To directly test changes, build the net-wireless/floss
package (it is only available on the zork-floss board right now).