On Thu, Jan 18, 2024 at 02:33:08PM +0100, Maciej Barć wrote:
A lot of Bazel bugs were just left to rot, even though they are invalid. There are work from users to get Bazel to a reasonable state, see: https://bugs.gentoo.org/918703 (plus comment #1)
# Unmasking this requires a sign-off from QA and treecleaners, since
# these packages require a ton of mental bandwidth to keep up to date
I would urge to reconsider leaving Bazel out of this; I do not think
that one is lost for now. Since I sometimes use Bazel myself, I will
work on adding a bazel-bin + virtual.
I will NOT however use/support Bazel for Gentoo packages nor eclasses.
Note that the current bazel ebuild uses the eclass. So if that's not
supported by anyone... Albeit seems(?) to only be for bazel_get_flags
so it should be easy to make it go standalone.
Also a virtual for -bin won't matter much if it's not intended for
use with Gentoo packaging. Users don't overly need to go through a
virtual and can just emerge bazel{,-bin} as wanted.
For all I care it could be reduced to a bin-only package if that's
easier and sufficient, not that I use bazel myself for anything to
have much of an opinion here.
That aside, bazel does sound far less bad than keeping tensorflow.
--
ionen
-----BEGIN PGP SIGNATURE-----
iQEzBAABCAAdFiEEx3SLh1HBoPy/yLVYskQGsLCsQzQFAmWpL08ACgkQskQGsLCs QzS9pggAvKstFReGbNOjTFDTRlajCRQmLN9rWYaGQlclnj82SQQNEot/LP/6CzWs 3Jrom/2PGYBBb8XObgLs+rG1oP6bBjm+OwDsR8HrkJxvX2afCxjlwwTgA8pZuBHe VY0u8mZeBhiahrhjNwxNonL4hn3IYx3ss6LoVds1H/e5QfhTDeK1k1S7JAHGYwya sYz+vZ/+kWfnNdLm5c37a6v9QrbUEQlAIM2eLMporCPRI8HLJ6YK4wHDHOza1QQp 6PkgU5rykuWmh0FrKcHC5rsBe3U9di/8KaNQhj0zZ0cZg9BzhsYo1pukaJDgUy8i MxIBLgkD9VJleO5A7QDB6+IX5OzBKw==
=DgUG
-----END PGP SIGNATURE-----
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)