dev-build/bazelisk: new package; add 1.19.0

Signed-off-by: Maciej Barć <xgqt@gentoo.org>

dev-build/bazelisk/Manifest

@@ -0,0 +1,2 @@
+DIST bazelisk-1.19.0-deps.tar.xz 2414272 BLAKE2B d044bafa94ce8d4fd9bc6dceb76368653c5052ed579be6f6a6fd37c68c821442f86fabcebc88eff118a414bd99e0e9b49dde5321130107da9c3c3563e7cba01b SHA512 57bafd7bb370f49cf2ff90596e25be8672dc4ed4f8466f8a969b49ce6b1bc57d6aff917065ec07bb04c634efb259d8e045213acb04ba1288c6a5f2a441eb2607
+DIST bazelisk-1.19.0.tar.gz 166002 BLAKE2B 052411a9f43ce511980b0d15fc87b9abe652759aa5b90e420bb3b248f5ae287000c84fb86df21b950bfc708addb36c9b109042526fc3c88d2d6939ce3e9cfc1a SHA512 32e4401d685f46f2b6cf0a26165fedc1f2eef71bcea939f96e0c03f0bb20f666dc3c7a191df51f978b79fcba7941d6a4a5cd211d9e5a42d3b24e4704a6df890e

dev-build/bazelisk/bazelisk-1.19.0.ebuild

@@ -0,0 +1,38 @@
+# Copyright 1999-2024 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit go-module
+
+DESCRIPTION="A user-friendly launcher for Bazel written in Go"
+HOMEPAGE="https://github.com/bazelbuild/bazelisk/"
+SRC_URI="
+	https://github.com/bazelbuild/${PN}/archive/refs/tags/v${PV}.tar.gz
+		-> ${P}.tar.gz
+	https://dev.gentoo.org/~xgqt/distfiles/deps/${P}-deps.tar.xz
+"
+
+LICENSE="Apache-2.0"
+SLOT="0"
+KEYWORDS="~amd64 ~x86"
+
+DOCS=( CONTRIBUTING.md README.md )
+
+src_compile() {
+	mkdir -p bin || die
+
+	local go_ldflags="-X main.BazeliskVersion=${PV}"
+	local -a go_buildargs=(
+		-ldflags "${go_ldflags}"
+		-o bin
+	)
+	ego build "${go_buildargs[@]}"
+}
+
+src_install() {
+	exeinto /usr/bin
+	doexe "bin/${PN}"
+
+	einstalldocs
+}

dev-build/bazelisk/metadata.xml

@@ -0,0 +1,20 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
+
+<pkgmetadata>
+  <maintainer type="person">
+    <email>xgqt@gentoo.org</email>
+    <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
+    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>
+  <upstream>
+    <bugs-to>https://github.com/bazelbuild/bazelisk/issues/</bugs-to>
+    <remote-id type="github">bazelbuild/bazelisk</remote-id>
+  </upstream>
+</pkgmetadata>