On 2020-04-08 19:43, Olek Wojnar wrote:
Bazel has suddenly become more important because it is preventing us from getting packages working that would help with the COVID-19 pandemic. Due to the significance, I am copying the Debian Med team as well as key people from this bug's history in the hopes of getting something moving quickly.On Tue, 22 May 2018 14:55:19 -0600 Kyle Moffett <kyle@moffetthome.net> wrote:I spent a while working on it off and on, but there is a decent amount of tweaking and other packaging work needed to get policy-compliant bazel packages. (E.G: There are quite a few binary JAR files shipped in the upstream tarball that don't necessarily match the versions in Debian). I just didn't have the spare time, especially now that I have a kid, to sink into one package.I can relate to the kid/time issues! ;) Have you had any time to work on it recently? Did you ever upload any of your work?In the meantime, I see that Bazel has an unofficial Ubuntu build [1]. Do you know anything about that? It seems like a good place for us to start if you aren't close to a product yourself.
That's the build Google provides that is built with Bazel itself, using a ton of vendored libraries. (Because that's how Google operates internally.)
Generally the pkg_deb output[1] is not really policy-compliant and more built from the ground up without any Debian tooling. So the /mere existence/ of that package (which was there from the beginning) does not help the quest of getting Bazel packaged for Debian, unfortunately.
Kind regards Philipp Kern, obviously not speaking for Google[1] https://github.com/bazelbuild/bazel/blob/f828b4c77805ad0ea6afecef798aa69d68bec8d4/scripts/packages/debian/BUILD#L69