Opened 4 years ago
Closed 4 years ago
#62691 closed defect (fixed)
bazel subports should not conflict
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | missa-prime (Mohamed Issa) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.6.4 |
| Keywords: | Cc: | cjones051073 (Chris Jones) | |
| Port: | bazel |
Description
In #62685 I saw:
Error: Can't install bazel-3.7 because conflicting ports are active: bazel-3.1
Ports named with suffixed versions should be simultaneously installable. They should not conflict with one another. This is important since apparently different software requires different versions of bazel to build successfully.
Change History (2)
comment:1 Changed 4 years ago by cjones051073 (Chris Jones)
comment:2 Changed 4 years ago by Chris Jones <jonesc@…>
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Yeah, this hasn't been a problem so far as only the tensor flow ports used bazel, and they also conflict. Now there is a bazel PG and more ports using it it makes sense to see if this can be done.