Added dev-vcs/lazygit-0.44.0

dev-vcs/lazygit/Manifest

@@ -0,0 +1 @@
+DIST lazygit-0.44.0.tar.gz 4712697 BLAKE2B a3da1ec65f8e3ad302f3979f615b63d1628c3df7b2b4c8ca60b30d818c0ca13fa97cf8a2216ff249adb4852622fb724a7295cc404446cff96018aefeed908017 SHA512 48cc51d8ffb92d92a04e821db69b9c0058cc2e327d796c9e5367b5e11e43c4335a1e2822d31116920744b00d901e8a8cc532aa98e75a0b5ee300db4aaa351a94

dev-vcs/lazygit/lazygit-0.44.0.ebuild

@@ -0,0 +1,34 @@
+# Copyright 1999-2024 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit go-module
+
+DESCRIPTION="Simple terminal UI for git commands"
+HOMEPAGE="https://github.com/jesseduffield/lazygit"
+SRC_URI="https://github.com/jesseduffield/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+S="${WORKDIR}/${P}"
+
+LICENSE="Apache-2.0 BSD ISC MIT Unlicense"
+SLOT="0"
+KEYWORDS="~amd64 ~arm64"
+
+RDEPEND="dev-vcs/git"
+
+DOCS=( {CODE-OF-CONDUCT,CONTRIBUTING,README}.md docs )
+
+src_compile() {
+	ego build -o bin/${PN} \
+		-ldflags "-X main.version=${PV}"
+}
+
+src_test() {
+	ego test ./... -short
+}
+
+src_install() {
+	dobin bin/${PN}
+	einstalldocs
+}

dev-vcs/lazygit/metadata.xml

@@ -0,0 +1,28 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "https://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+  <maintainer type="person">
+    <email>torokhov-s-a@yandex.ru</email>
+    <name>Sergey Torokhov</name>
+  </maintainer>
+  <longdescription lang="en">
+    A simple terminal UI for both docker and docker-compose, written in Go with the gocui library.
+    Minor rant incoming: Something's not working? Maybe a service is down. docker-compose ps.
+    Yep, it's that microservice that's still buggy. No issue, I'll just restart it: docker-compose restart.
+    Okay now let's try again. Oh wait the issue is still there. Hmm. docker-compose ps.
+    Right so the service must have just stopped immediately after starting.
+    I probably would have known that if I was reading the log stream, but there is a lot of clutter in there from other services.
+    I could get the logs for just that one service with docker compose logs --follow myservice but that dies everytime the service dies so I'd need to run that command every time I restart the service.
+    I could alternatively run docker-compose up myservice and in that terminal window if the service is down I could just up it again,
+    but now I've got one service hogging a terminal window even after I no longer care about its logs.
+    I guess when I want to reclaim the terminal realestate I can do ctrl+P,Q, but... wait, that's not working for some reason.
+    Should I use ctrl+C instead? I can't remember if that closes the foreground process or kills the actual service.
+    What a headache! Memorising docker commands is hard. Memorising aliases is slightly less hard.
+    Keeping track of your containers across multiple terminal windows is near impossible.
+    What if you had all the information you needed in one terminal window with every common command living one keypress away (and the ability to add custom commands as well).
+    Lazydocker's goal is to make that dream a reality.
+  </longdescription>
+  <upstream>
+    <remote-id type="github">jesseduffield/lazydocker</remote-id>
+  </upstream>
+</pkgmetadata>