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: Thu, 19 Aug 2021 19:18:39 +0000 (UTC)	[thread overview]
Message-ID: <1629400380.2f9ce26aa7b491dddc688de7a3d4ef97c3b9a8e5.SergeyTorokhov@gentoo> (raw)

commit:     2f9ce26aa7b491dddc688de7a3d4ef97c3b9a8e5
Author:     Sergey Torokhov <torokhov-s-a <AT> yandex <DOT> ru>
AuthorDate: Thu Aug 19 19:13:00 2021 +0000
Commit:     Sergey Torokhov <torokhov-s-a <AT> yandex <DOT> ru>
CommitDate: Thu Aug 19 19:13:00 2021 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=2f9ce26a

dev-vcs/lazygit: 0.29 version bump

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

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

diff --git a/dev-vcs/lazygit/Manifest b/dev-vcs/lazygit/Manifest
index 2c9b309ce..9bd43cef6 100644
--- a/dev-vcs/lazygit/Manifest
+++ b/dev-vcs/lazygit/Manifest
@@ -1,3 +1,4 @@
 DIST lazygit-0.27.4.tar.gz 3214405 BLAKE2B 123c2b7ca1bb63fa7d7a40b4c8a56b3f39b651c214ad55179dd07cd81588341589419759207263bbf809da89218e35d2c6185c79bcfd9ee59480ed66d67506dc SHA512 a053d4d3e3458ad33c415a7e9d4286a52b23429babae715afacc61a91185a309d78951cc617ad182cdb59aa53ce48dae9ce38f65c38c8364eaac88d92e478c9d
 DIST lazygit-0.28.1.tar.gz 3222346 BLAKE2B 8cfb3cd59c991cefb3de652c49ef8bb0f94f7f1da6af9fa62e4288383ae14e64644a82fb8ca4d2037fa6b39a54b6b716b9851d42e023ea0a81e2b9d865f6df69 SHA512 8e477216f2f93b3e1d9a5d2c771d05a180e5f193a84afb6d8f93b6fa1d91a7efac89e6e43c5c1c0034c19a19f7e6dada6eed69402cabf5ca2860284fb2c6e232
 DIST lazygit-0.28.2.tar.gz 3223174 BLAKE2B 678a44f4109446e7490cc75b4bb2f0195357a8f6dc2539251de7b829b11ef0a7b8d125bb518f7d6822df62bf9922026ba2948d4d6318ca9e18dafcca7ff9792d SHA512 e7002089194c572fffe8329bd245d4db64fb71cb73c63f07b950da845ecdc85c70c8bea682d2b4aa1c9b38f8cf5270cd24d3bb41eff8a26d31be58eddcdf41ce
+DIST lazygit-0.29.tar.gz 3385768 BLAKE2B 4968a45572d85a3af84fc8f459dbab1cfd3a70954c650f16ddd8e937a810b590c974642e94b26614f4b24166b6c4db2fc8dd2538052875d827fdecc8bf8acb18 SHA512 f24d63a01bc64e2704805a20437af7ad0304921c2b4084f64014f9a8d9d9711ef02f4cdcf09ee9955ea5f2ef4f94de58c9ecc55fa7cb05fc59a89c7d8c9237d7

diff --git a/dev-vcs/lazygit/lazygit-0.29.ebuild b/dev-vcs/lazygit/lazygit-0.29.ebuild
new file mode 100644
index 000000000..233a104b0
--- /dev/null
+++ b/dev-vcs/lazygit/lazygit-0.29.ebuild
@@ -0,0 +1,36 @@
+# Copyright 1999-2021 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:[~2021-08-19 19:18 UTC|newest]

Thread overview: 70+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-19 19:18 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-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-26  8:44 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=1629400380.2f9ce26aa7b491dddc688de7a3d4ef97c3b9a8e5.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