Can I have two different versions of the same Rust library in one Bazel project? #144
Comments
|
cc @acmcarther |
|
cargo-raze doesn't have a good story for this for now. If cargo itself has one, I think we could probably tweak raze to provide access to these types of dependencies. Is there syntax in cargo for including multiple versions of the same dep? We currently do pull multiple versions of the same dep for dependency resolution, but up until now there wasn't a case made for providing workspace-visible aliases to them. For now, you might be able to address this in limited situations by having a second raze directory, but that would probably duplicate many other dependencies and could result in having multiple incompatible versions of the same types. |
|
Aliases do this and I should work on getting it merged |
@GregBowyer Yes, please! |
|
#187 should do this for you |
|
@GregBowyer Thanks a lot! Hopefully your PR will be merged soon! |
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Nov 6, 2020
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Nov 6, 2020
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Nov 6, 2020
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Nov 6, 2020
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Nov 7, 2020
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Nov 7, 2020
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Nov 9, 2020
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Feb 4, 2021
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Feb 4, 2021
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Feb 5, 2021
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Apr 23, 2021
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Apr 23, 2021
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Apr 23, 2021
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Apr 23, 2021
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Apr 23, 2021
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Apr 23, 2021
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
GregBowyer
added a commit
to GregBowyer/cargo-raze
that referenced
this issue
Apr 24, 2021
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi! Can I have two different versions of the same Rust library in one Bazel project?
For example, some projects within one Bazel repository can depend on
futures-0.1.x, but some can requirefutures-0.3.x. How to handle such use case using cargo-raze?The text was updated successfully, but these errors were encountered: