Github messages for voidlinux
 help / color / mirror / Atom feed
From: kkga <kkga@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: mcfly-0.5.7
Date: Sat, 17 Jul 2021 14:54:32 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32020@inbox.vuxu.org> (raw)

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

There is a new pull request by kkga against master on the void-packages repository

https://github.com/kkga/void-packages mcfly
https://github.com/void-linux/void-packages/pull/32020

New package: mcfly-0.5.7
<!-- Mark items with [x] where applicable -->

#### General

- [x] This is a new package and it conforms to the
  [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?

- [ ] I use the packages affected by the proposed changes on a regular basis and
  confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!--
#### Does it build and run successfully?
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [x] I built this PR locally for my native architecture, (x86-glibc)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->


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

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

From ccaaf344ed8df99c31e67fb1822c01c18242260d Mon Sep 17 00:00:00 2001
From: Gadzhi Kharkharov <me@kkga.me>
Date: Sat, 17 Jul 2021 15:45:49 +0300
Subject: [PATCH] New package: mcfly-0.5.7

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

diff --git a/srcpkgs/mcfly/template b/srcpkgs/mcfly/template
new file mode 100644
index 000000000000..6b7551daacdb
--- /dev/null
+++ b/srcpkgs/mcfly/template
@@ -0,0 +1,15 @@
+# Template file for 'mcfly'
+pkgname=mcfly
+version=0.5.7
+revision=1
+build_style=cargo
+short_desc="Fly through your shell history"
+maintainer="Gadzhi Kharkharov <me@kkga.me>"
+license="MIT"
+homepage="https://github.com/cantino/mcfly"
+distfiles="https://github.com/cantino/mcfly/archive/v${version}.tar.gz"
+checksum=8132e47b1354fc985c8d5553d5c7fd6e9524aa3dc938ae5ac90c01967a7f61c0
+
+post_install() {
+	vlicense LICENSE
+}

             reply	other threads:[~2021-07-17 12:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-17 12:54 kkga [this message]
2021-07-19 22:05 ` [PR PATCH] [Updated] " kkga
2021-10-11  7:23 ` [PR PATCH] [Closed]: " kkga

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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32020@inbox.vuxu.org \
    --to=kkga@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).