Hi Stefano,
this is a good new. However, the issues with Bazel is not only that it
requires a team of Google engineers to package it for Debian, but also
for using it, even for a seemingly not too complex package as Benacount:
the Beancount's Bazel build definition is not working on macOS, and it
cannot work on Windows (it uses the native autotools build for some of
the dependencies, without AFAIK a way to use these dependencies from
external sources, this does not make it easy to use Bazel to build
distribution packages).
I found much more rewarding to work on a Meson build definition rather
than debugging this. It only took a few hours to write it, including
writing Meson build definitions for most of the dependencies. This work
can be found here:
https://github.com/beancount/beancount/pull/612
It supports out of the box building with dependencies from the OS or
built as part of the same build. It is tested and working on macOS and
GNU/Linux. The only thing that is not supported but is done by Bazel, is
building in an environment that does not have Bison: Bison is byzantine
enough that I gave up trying to write a Meson build definition for it.
I haven't tried it on Windows, but in principle it should work just fine
there too, once you get Bison (I think it exist pre-built for Windows
somewhere out there).
I am working to be able to package that into a Python sdist and wheels
that can be uploaded to PyPI. However, as of now, the c++ code in
Beancount is not hooked up yet, thus this is progressing with very low
priority.
Cheers,
Dan