Github messages for voidlinux
 help / color / mirror / Atom feed
From: zen0bit <zen0bit@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: lazycli-0.1.15
Date: Sat, 22 Apr 2023 06:54:22 +0200	[thread overview]
Message-ID: <20230422045422.M-1_3CYuru7fDzclARCbLsb2cywGdXhRW0nQRBaU5sw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43472@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 478 bytes --]

There is an updated pull request by zen0bit against master on the void-packages repository

https://github.com/oSoWoSo/VUR lazycli
https://github.com/void-linux/void-packages/pull/43472

New package: lazycli-0.1.15

#### Testing the changes
- I tested the changes in this PR: **briefly**

#### Local build testing
- I built this PR locally for my native architecture, (x64 glibc)


A patch file from https://github.com/void-linux/void-packages/pull/43472.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-lazycli-43472.patch --]
[-- Type: text/x-diff, Size: 1244 bytes --]

From 3ebef7732171af3e6e354fbd4c969d6b2a634dc4 Mon Sep 17 00:00:00 2001
From: zenobit <zen@osowoso.xyz>
Date: Sun, 16 Apr 2023 07:09:10 +0200
Subject: [PATCH] New package: lazycli-0.1.15

---
 srcpkgs/lazycli/template | 28 ++++++++++++++++++++++++++++
 1 file changed, 28 insertions(+)
 create mode 100644 srcpkgs/lazycli/template

diff --git a/srcpkgs/lazycli/template b/srcpkgs/lazycli/template
new file mode 100644
index 000000000000..be4ffdb59a16
--- /dev/null
+++ b/srcpkgs/lazycli/template
@@ -0,0 +1,28 @@
+# Template file for 'lazycli'
+pkgname=lazycli
+version=0.1.15
+revision=1
+build_style=cargo
+#configure_args=""
+#make_build_args="CONFIG_DIR_ENV_VAR=/usr/share/lazycli"
+make_install_args="CONFIG_DIR_ENV_VAR=/usr/share/lazycli"
+#conf_files=""
+short_desc="Turn static CLI commands into TUIs with ease"
+maintainer="zenobit <zen@osowoso.xyz>"
+license="MIT"
+homepage="https://github.com/jesseduffield/lazycli"
+#changelog=""
+distfiles="https://github.com/jesseduffield/lazycli/archive/refs/tags/v${version}.tar.gz"
+checksum=66f4c4c5bedf4d3ceb35aebc1d7f18663c7250ac47241fea18108c0741bf2019
+
+do_build() {
+	cargo build --release
+}
+
+do_install() {
+	vbin target/release/lazycli
+}
+
+post_install() {
+	vlicense LICENSE
+}

  parent reply	other threads:[~2023-04-22  4:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-16  4:54 [PR PATCH] New package: lazycli 0.1.15 zen0bit
2023-04-16  5:10 ` [PR PATCH] [Updated] New package: lazycli-0.1.15 zen0bit
2023-04-19 20:58 ` zen0bit
2023-04-22  4:54 ` zen0bit [this message]
2023-04-22  5:09 ` zen0bit
2023-05-04 10:49 ` zen0bit
2023-09-03  4:38 ` zen0bit
2023-09-03  4:40 ` zen0bit
2023-09-04 13:52 ` zen0bit
2023-10-10 15:35 ` zen0bit
2024-01-09  1:46 ` github-actions
2024-01-10  2:51 ` [PR PATCH] [Updated] " zen0bit
2024-01-10  2:53 ` zen0bit
2024-04-11  1:45 ` github-actions
2024-04-25  1:46 ` [PR PATCH] [Closed]: " github-actions

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=20230422045422.M-1_3CYuru7fDzclARCbLsb2cywGdXhRW0nQRBaU5sw@z \
    --to=zen0bit@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).