Added app-containers/lazydocker-0.21.1

app-containers/lazydocker/Manifest

@@ -0,0 +1 @@
+DIST lazydocker-0.21.1.tar.gz 11992745 BLAKE2B 1377a43dcab6d004e8eb4f16d7295efddc44a26abba41775ffa1aaf574ccd62ec6db235648ca55d3109639376d688548c7e79bd4e4d81ee37c8ecca5470f4f5b SHA512 8670a2b32091a806845a458f3f2edffb0f2d56784bcc3584fa854fc2772209231fd81c0ac1eb4dcb1792e8e511bbf6113983471351102c7d8e0fe04a5e7f68e0

app-containers/lazydocker/lazydocker-0.21.1.ebuild

@@ -0,0 +1,31 @@
+# Copyright 1999-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=8
+
+inherit go-module
+
+DESCRIPTION="The lazier way to manage everything docker"
+HOMEPAGE="https://github.com/jesseduffield/lazydocker"
+SRC_URI="https://github.com/jesseduffield/${PN}/archive/v${PV}.tar.gz -> ${P}.tar.gz"
+
+LICENSE="Apache-2.0 BSD ISC MIT Unlicense"
+SLOT="0"
+KEYWORDS="~amd64 ~arm64"
+
+S="${WORKDIR}/${P}"
+
+RDEPEND=">=app-containers/docker-cli-1.13
+	>=app-containers/docker-compose-1.23.2"
+
+DOCS=( {CODE-OF-CONDUCT,CONTRIBUTING,README}.md docs )
+
+src_compile() {
+	ego build -o bin/${PN} \
+		-ldflags "-X main.version=${PV}"
+}
+
+src_install() {
+	dobin bin/${PN}
+	einstalldocs
+}

app-containers/lazydocker/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>

metadata/md5-cache/app-containers/lazydocker-0.21.1

@@ -0,0 +1,14 @@
+BDEPEND=>=dev-lang/go-1.18 app-arch/unzip
+DEFINED_PHASES=compile install unpack
+DESCRIPTION=The lazier way to manage everything docker
+EAPI=8
+HOMEPAGE=https://github.com/jesseduffield/lazydocker
+INHERIT=go-module
+KEYWORDS=~amd64 ~arm64
+LICENSE=Apache-2.0 BSD ISC MIT Unlicense
+RDEPEND=>=app-containers/docker-cli-1.13 >=app-containers/docker-compose-1.23.2
+RESTRICT=strip
+SLOT=0
+SRC_URI=https://github.com/jesseduffield/lazydocker/archive/v0.21.1.tar.gz -> lazydocker-0.21.1.tar.gz
+_eclasses_=multiprocessing	b4e253ab22cef7b1085e9b67c7a3b730	toolchain-funcs	862d337d98edb576796827be2c6b11ca	multilib	c19072c3cd7ac5cb21de013f7e9832e0	go-module	8624eede24936fd7666e5298e5332f22
+_md5_=c5ecd6005ff7d55b9b7d728af91848d9