public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sergey Torokhov" <torokhov-s-a@yandex.ru>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-vcs/lazygit/
Date: Sat, 26 Dec 2020 08:44:16 +0000 (UTC)	[thread overview]
Message-ID: <1608972159.568e7788407a4599cd1a28d09668605b496c8f56.SergeyTorokhov@gentoo> (raw)

commit:     568e7788407a4599cd1a28d09668605b496c8f56
Author:     Sergey Torokhov <torokhov-s-a <AT> yandex <DOT> ru>
AuthorDate: Sat Dec 26 08:42:39 2020 +0000
Commit:     Sergey Torokhov <torokhov-s-a <AT> yandex <DOT> ru>
CommitDate: Sat Dec 26 08:42:39 2020 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=568e7788

dev-vcs/lazygit: 0.24.2 version bump

Signed-off-by: Sergey Torokhov <torokhov-s-a <AT> yandex.ru>

 dev-vcs/lazygit/Manifest              |  1 +
 dev-vcs/lazygit/lazygit-0.24.2.ebuild | 36 +++++++++++++++++++++++++++++++++++
 2 files changed, 37 insertions(+)

diff --git a/dev-vcs/lazygit/Manifest b/dev-vcs/lazygit/Manifest
index aabf37b2..dee25348 100644
--- a/dev-vcs/lazygit/Manifest
+++ b/dev-vcs/lazygit/Manifest
@@ -1,3 +1,4 @@
 DIST lazygit-0.20.9.tar.gz 9196030 BLAKE2B 7fd64d06b3036926b00cc64f684d48a3791561e9b48f4bfbc2134e019caf4c96f8a37e2a1d33c79cab9a840b20f212f999f81d1e5a9763e2902332c298ede613 SHA512 d38fd390076a24b914309b6ecb506fc7b21e48c0bfab14aee5ff3bb7bcb591f47bf82051e5442ca4d4d2a0d864eb1554a64c594aefb130ec4f07861128d124dd
 DIST lazygit-0.22.9.tar.gz 9232631 BLAKE2B 50febf0727dc3fff0e61b158bc37df4128cdc9934a42b113612896a3712fb7cd0ce0a0860eec88cbbde289fd08fb492e851937be549a2036ad993bdeb3a101ae SHA512 9d4dc92762099c141e56bbb386217ea2028ba6a78d6bb5d54ef9c022e447a1b9fa2ce37d6e2813411fe6fa4f5192753beec8b136838aefe067019fd0820225e1
 DIST lazygit-0.23.7.tar.gz 2144614 BLAKE2B d18aaa19212ec9e6ed7d3b406d3e1f6413f6c15bf6a8c7c99cb8a2b01b9388db3f1ad04c485782e0823415cec3c6b461cf942583ef0ac744cb18270c8fc943b1 SHA512 ffc827a08a3ba99afa339cee48b9e10267bc4aa27592d43ec1e4be80a7b4f9e628f286b50a1940a59a5cfa96121de6ce4247ec91642a8798dba8ca42232596b9
+DIST lazygit-0.24.2.tar.gz 2155627 BLAKE2B 6ed6c44590f0585935ebdb8374ba7649df84092cf752b17f3ab0791f55eb8516de9530fbc18891aeb9acfb1b743804df87c679f8cebabcbd353d563e23cacd5a SHA512 f380dec647384f0084c4c13b8ca43a8d97411c83c4c66ef02645c785054b3a7e2210d5a1ce98676c6d190beccf51f21ecd38851598f7652ff087ac73addbd097

diff --git a/dev-vcs/lazygit/lazygit-0.24.2.ebuild b/dev-vcs/lazygit/lazygit-0.24.2.ebuild
new file mode 100644
index 00000000..df46884b
--- /dev/null
+++ b/dev-vcs/lazygit/lazygit-0.24.2.ebuild
@@ -0,0 +1,36 @@
+# Copyright 1999-2020 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+EGO_PN="github.com/jesseduffield/lazygit"
+
+inherit golang-build golang-vcs-snapshot
+
+DESCRIPTION="Lazygit, a 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"
+
+LICENSE="MIT"
+SLOT="0"
+KEYWORDS="~amd64"
+IUSE="doc"
+
+DEPEND=( sys-libs/glibc )
+RDEPEND=(
+	${DEPEND}
+	dev-vcs/git
+)
+
+DOCS=( src/${EGO_PN}/{CONTRIBUTING,README}.md )
+
+src_compile() {
+	GOPATH="${S}" go build -v -o bin/lazygit src/${EGO_PN}/main.go || die
+}
+
+src_install() {
+	dobin bin/lazygit
+
+	use doc && dodoc -r "src/${EGO_PN}/docs/."
+	einstalldocs
+}


             reply	other threads:[~2020-12-26  8:44 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-26  8:44 Sergey Torokhov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-18 18:33 [gentoo-commits] repo/proj/guru:dev commit in: dev-vcs/lazygit/ Sergey Torokhov
2024-09-09  0:02 Sergey Torokhov
2024-09-08 23:57 Sergey Torokhov
2024-07-26 20:49 Philippe-Alexandre Mathieu
2024-06-15 15:06 Sergey Torokhov
2024-05-06 20:27 Sergey Torokhov
2024-04-28 21:43 Lucio Sauer
2024-03-24 14:30 Sergey Torokhov
2023-08-21 19:21 Sergey Torokhov
2023-08-21 19:21 Sergey Torokhov
2023-08-08 18:44 Sergey Torokhov
2023-08-06 15:16 Sergey Torokhov
2023-07-24 18:09 Sergey Torokhov
2023-07-23  9:07 Sergey Torokhov
2023-07-23  9:07 Sergey Torokhov
2023-07-22 16:56 Sergey Torokhov
2023-07-21 17:05 Sergey Torokhov
2023-05-03 19:43 Sergey Torokhov
2023-05-03 19:43 Sergey Torokhov
2023-02-01 23:01 Sergey Torokhov
2023-01-18 21:34 Sergey Torokhov
2022-11-14 11:46 Sergey Torokhov
2022-07-20 22:34 Sergey Torokhov
2022-03-17 19:19 Sergey Torokhov
2022-02-24  7:54 Anna Vyalkova
2022-02-23 13:44 Anna Vyalkova
2022-02-20 19:21 Sergey Torokhov
2022-02-20 19:21 Sergey Torokhov
2021-12-12 11:50 Sergey Torokhov
2021-12-12 11:50 Sergey Torokhov
2021-11-10 13:39 Sergey Torokhov
2021-11-09 20:50 Sergey Torokhov
2021-10-27  0:22 Sergey Torokhov
2021-10-24 15:06 Sergey Torokhov
2021-10-15 16:20 Sergey Torokhov
2021-08-19 19:18 Sergey Torokhov
2021-08-19 19:18 Sergey Torokhov
2021-07-18 12:16 Sergey Torokhov
2021-05-25  8:10 Anna Vyalkova
2021-04-21 20:34 Sergey Torokhov
2021-04-21 20:34 Sergey Torokhov
2021-04-11 10:35 Sergey Torokhov
2021-04-10 18:04 Sergey Torokhov
2021-04-08 19:07 Sergey Torokhov
2021-03-14 21:46 Sergey Torokhov
2021-03-14 21:46 Sergey Torokhov
2021-02-24 17:52 Sergey Torokhov
2021-02-24 17:52 Sergey Torokhov
2020-12-09 23:40 Sergey Torokhov
2020-11-07 19:07 Sergey Torokhov
2020-10-14 20:47 Sergey Torokhov
2020-10-10 13:34 Sergey Torokhov
2020-10-10  0:37 Sergey Torokhov
2020-10-10  0:37 Sergey Torokhov
2020-09-20 18:05 Sergey Torokhov
2020-08-27 19:11 Sergey Torokhov
2020-08-25 17:59 Sergey Torokhov
2020-07-15 19:39 Sergey Torokhov
2020-07-14 18:12 Sergey Torokhov
2020-07-14 18:12 Sergey Torokhov
2020-07-12 15:07 Sergey Torokhov
2020-07-11 23:50 Sergey Torokhov
2020-05-19 23:12 Sergey Torokhov
2020-05-13 19:05 Sergey Torokhov
2020-05-13 18:55 Sergey Torokhov
2020-04-22 10:12 Sergey Torokhov
2020-04-21  0:32 Sergey Torokhov
2020-04-09 17:52 Sergey Torokhov
2020-04-08 11:58 Sergey Torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1608972159.568e7788407a4599cd1a28d09668605b496c8f56.SergeyTorokhov@gentoo \
    --to=torokhov-s-a@yandex.ru \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox