All of these will be using app-alternatives/ninja anyway as they're not calling ninja-reference, so make the dep reflect reality.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3a05edbf9ab208a8959f323dd70a70d9977f86d9 commit 3a05edbf9ab208a8959f323dd70a70d9977f86d9 Author: Matt Jolly <kangie@gentoo.org> AuthorDate: 2025-02-23 23:45:44 +0000 Commit: Matt Jolly <kangie@gentoo.org> CommitDate: 2025-02-24 04:52:10 +0000 www-client/chromium: dev-build/ninja -> app-alternatives/ninja Enabling the use of alternative ninja implementations as per the bug below. If it proves to cause issues due to GN generating build files that don't work with a not-actually-ninja ninja impl we can switch back. Closes: https://github.com/gentoo/gentoo/pull/40492 Closes: https://bugs.gentoo.org/949551 Signed-off-by: Matt Jolly <kangie@gentoo.org> www-client/chromium/chromium-133.0.6943.126.ebuild | 2 +- www-client/chromium/chromium-134.0.6998.23.ebuild | 2 +- www-client/chromium/chromium-135.0.7023.0.ebuild | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-)