You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2022. It is now read-only.
cargo vendor is something some companies use to either ultra lock down their dependencies or satisfy requirements in their massive monorepos.
My current thought is that vendoring support would be done as a rule or macro which defines a runnable target that would both perform the vendoring and write the BUILD files to the appropriate directories.
Users could then run bazel run //:cargo_bazel_vendor to vendor crates into their workspace and have BUILD files rendered into place. Maybe this rule could even support a packages attribute which allows you to inline the desired crates.
Again, just thoughts, not sure if or when this should be done.
The text was updated successfully, but these errors were encountered:
cargo vendor is something some companies use to either ultra lock down their dependencies or satisfy requirements in their massive monorepos.
My current thought is that vendoring support would be done as a rule or macro which defines a runnable target that would both perform the vendoring and write the BUILD files to the appropriate directories.
Users could then run
bazel run //:cargo_bazel_vendor
to vendor crates into their workspace and have BUILD files rendered into place. Maybe this rule could even support apackages
attribute which allows you to inline the desired crates.Again, just thoughts, not sure if or when this should be done.
The text was updated successfully, but these errors were encountered: