Bug 239461 - Keep Old Versions of devel/bazel
Summary: Keep Old Versions of devel/bazel
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-07-26 11:14 UTC by Anthony Donnelly
Modified: 2019-08-02 15:08 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (aehlig)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Anthony Donnelly 2019-07-26 11:14:00 UTC 
Some programs require specific versions of bazel to build. For example tensorflow 1.13.0 needs bazel 0.22.0 while it fails with the ports latest version 0.28.0.

Is it possible to keep old versions but rename them. E.g devel/bazel22 or devel/bazel28 so that a BUILD_DEPEND can depend on the correct version. Of course conflicts would need to be set or an alternative way suck as setting a program suffix.
Comment 1 Klaus Aehlig 2019-08-02 14:38:59 UTC 
It is no problem to install and user several versions of bazel in parallel, provided the binaries are called differently; the latter can be easily achieved by adding a version suffix to the binary.

However, I'm unsure which versions to preserve. There is new release of bazel every month, so keeping really all versions would add up very quickly. Are there any suggestions about which specific versions of bazel to keep (besides devel/bazel for the latest release)? Maybe just the version needed specifically for tensorflow?
Comment 2 Anthony Donnelly 2019-08-02 15:08:03 UTC 
I think really what is needed is a USES case for bazel. As for tensorflow. I moved to the latest version but I still need to ship with it a bazelrc to set the repository for downloads as local to prevent bazel downloading sources.I don't think this is an issue for the maintainer and more of the ports. As I moved to the latest version of tensorflow the I no longer need an older version of bazel. I will close this bug.