public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: David Seifert <soap@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 14:56:11 +0100	[thread overview]
Message-ID: <9b7e1e3474510acb7bae67f66d07a95430ac45b2.camel@gentoo.org> (raw)
In-Reply-To: <d0e47768-fd83-4076-864d-c0c153fb5c63@gentoo.org>

On Thu, 2024-01-18 at 14:33 +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.
> 

Then fix the bugs that are open right now (and keep it masked), since I
don't believe Bazel is much better than the rest. Once the overwhelming
majority of bugs are fixed, we can see again.

That said, given how brittle all of this stuff is and how little Google
cares about FOSS users, I don't believe this to be sustainable path
forward.

> I will NOT however use/support Bazel for Gentoo packages nor eclasses.
> 
> On 18.01.2024 13:53, David Seifert wrote:
> > # David Seifert <soap@gentoo.org> (2024-01-18)
> > # Unmaintained set of packages. Overall, TensorFlow is ill-suited
> > for
> > # distro packaging, since it's entangled with tons of googleware and
> > # continually breaks on minor dependency updates coupled with a
> > # byzantine build system. These 5 packages together have a total of
> > # 54 bugs reported against them, with zero activity from the
> > maintainer.
> > #
> > # Unmasking this requires a sign-off from QA and treecleaners, since
> > # these packages require a ton of mental bandwidth to keep up to
> > date
> > # and Google's general unwillingness to take community input quickly
> > # leads to maintainer burnout.
> > # Use sci-libs/pytorch as a modern alternative with better
> > packaging.
> > # Removal on 2024-02-17. Bug #922374
> > dev-build/bazel
> > sci-libs/keras
> > sci-libs/tensorflow
> > sci-libs/tensorflow-estimator
> > sci-visualization/tensorboard
> > 
> 
> -- 
> Have a great day!
> 
> ~ Maciej XGQT Barć
> 
> xgqt@gentoo.org
> Gentoo Linux developer
> (dotnet, emacs, math, ml, nim, scheme, sci)
> https://wiki.gentoo.org/wiki/User:Xgqt
> 9B0A 4C5D 02A3 B43C 9D6F D6B1 14D7 4A1F 43A6 AC3C



  reply	other threads:[~2024-01-18 13:56 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 [this message]
2024-01-18 14:01   ` Ionen Wolkens
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=9b7e1e3474510acb7bae67f66d07a95430ac45b2.camel@gentoo.org \
    --to=soap@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