From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-dev-announce] Last rites: dev-build/bazel, sci-libs/keras, sci-libs/tensorflow, sci-libs/tensorflow-estimator, sci-visualization/tensorboard
Date: Thu, 18 Jan 2024 09:01:51 -0500 [thread overview]
Message-ID: <ZakvT933S0fOiK-0@eversor> (raw)
In-Reply-To: <d0e47768-fd83-4076-864d-c0c153fb5c63@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1316 bytes --]
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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-01-18 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 12:53 [gentoo-dev] Last rites: dev-build/bazel, sci-libs/keras, sci-libs/tensorflow, sci-libs/tensorflow-estimator, sci-visualization/tensorboard David Seifert
2024-01-18 13:33 ` [gentoo-dev] Re: [gentoo-dev-announce] " Maciej Barć
2024-01-18 13:56 ` David Seifert
2024-01-18 14:01 ` Ionen Wolkens [this message]
2024-01-18 17:53 ` [gentoo-dev] " Alfredo Tupone
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZakvT933S0fOiK-0@eversor \
--to=ionen@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox