[gentoo-commits] repo/gentoo:master commit in: dev-build/bazelisk/

["Maciej Barć" <xgqt@gentoo.org>]

commit:     6e4fb2b43339fa5df77a346fb71235b30844ab58
Author:     Maciej Barć <xgqt <AT> gentoo <DOT> org>
AuthorDate: Mon Mar  4 17:08:49 2024 +0000
Commit:     Maciej Barć <xgqt <AT> gentoo <DOT> org>
CommitDate: Mon Mar  4 21:56:44 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=6e4fb2b4

dev-build/bazelisk: support bazel-symlink

Closes: https://bugs.gentoo.org/926104
Signed-off-by: Maciej Barć <xgqt <AT> gentoo.org>

 .../bazelisk/{bazelisk-1.19.0.ebuild => bazelisk-1.19.0-r1.ebuild} | 5 +++++
 dev-build/bazelisk/metadata.xml                                    | 7 +++++--
 2 files changed, 10 insertions(+), 2 deletions(-)

diff --git a/dev-build/bazelisk/bazelisk-1.19.0.ebuild b/dev-build/bazelisk/bazelisk-1.19.0-r1.ebuild
similarity index 88%
rename from dev-build/bazelisk/bazelisk-1.19.0.ebuild
rename to dev-build/bazelisk/bazelisk-1.19.0-r1.ebuild
index 4cea472f3598..9b18306d7e1b 100644
--- a/dev-build/bazelisk/bazelisk-1.19.0.ebuild
+++ b/dev-build/bazelisk/bazelisk-1.19.0-r1.ebuild
@@ -16,6 +16,7 @@ SRC_URI="
 LICENSE="Apache-2.0"
 SLOT="0"
 KEYWORDS="~amd64 ~arm64 ~x86"
+IUSE="+bazel-symlink"
 
 DOCS=( CONTRIBUTING.md README.md )
 
@@ -34,5 +35,9 @@ src_install() {
 	exeinto /usr/bin
 	doexe "bin/${PN}"
 
+	if use bazel-symlink ; then
+		dosym -r /usr/bin/bazelisk /usr/bin/bazel
+	fi
+
 	einstalldocs
 }

diff --git a/dev-build/bazelisk/metadata.xml b/dev-build/bazelisk/metadata.xml
index 032d00abaf95..de81e5f355e3 100644
--- a/dev-build/bazelisk/metadata.xml
+++ b/dev-build/bazelisk/metadata.xml
@@ -7,12 +7,15 @@
     <name>Maciej Barć</name>
   </maintainer>
   <longdescription>
-    Bazelisk is a wrapper for Bazel written in Go. It automatically picks
-    a good version of Bazel given your current working directory, downloads it
+    Bazelisk is a wrapper for Bazel written in Go. It automatically picks a
+    good version of Bazel given your current working directory, downloads it
     from the official server (if required) and then transparently passes
     through all command-line arguments to the real Bazel binary. You can call
     it just like you would call Bazel.
   </longdescription>
+  <use>
+    <flag name="bazel-symlink">Install bazel symlink that points to bazelisk</flag>
+  </use>
   <upstream>
     <bugs-to>https://github.com/bazelbuild/bazelisk/issues/</bugs-to>
     <remote-id type="github">bazelbuild/bazelisk</remote-id>