Closed sena-otus closed 11 months ago
Bazel 4.x is several years out of date. If you must stick with that, my advice is use an older version of rules_pkg, from when 4.x was still current.
Bazel 4.x is several years out of date. If you must stick with that, my advice is use an older version of rules_pkg, from when 4.x was still current.
I did not know that it is out of date. I want to learn bazel and installed one from the current stable Debian 12 (bookworm). It is strange that they ship the outdated version. What will be the recommended way to install it on Debian?
Bazel 4.x is several years out of date. If you must stick with that, my advice is use an older version of rules_pkg, from when 4.x was still current.
Debian package is referenced on Basel website. May be they should highlight that package shipped with Debian is outdated and must not be used, instead of just linking to Debian site. Should I report that?
Bazel 4.x is several years out of date. If you must stick with that, my advice is use an older version of rules_pkg, from when 4.x was still current.
It will be also good (remember examples are for newbies!) if you will check bazel version in BUILD script and produce some meaningful error message like "Your are using bazel 4.2.3 it is not supported, please upgrade to 10.x".
At least in CMake you can do that.
Bazel 4.x is several years out of date. If you must stick with that, my advice is use an older version of rules_pkg, from when 4.x was still current.
Debian package is referenced on Basel website. May be they should highlight that package shipped with Debian is outdated and must not be used, instead of just linking to Debian site. Should I report that?
You could. The Bazel team does not create the Debian packages, so we don't know if they are out of date.
I opened the issue in the Bazel repo. https://github.com/bazelbuild/bazel/issues/20133
What about checking bazel version in BUILD sproduce some meaningful error message like "Your are using bazel 4.2.3 it is not supported, please upgrade to 10.x"?
This is the wrong place to do that. It should be a bazel feature.
One rough idea is that WORKSPACE and MODULE.bazel should have an ability to set minimal bazel version. If you try to build with an early bazel version it fails there.
$ cd rules_pkg/examples/naming_package_files