Github messages for voidlinux
 help / color / mirror / Atom feed
From: kawaiiamber <kawaiiamber@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] New package: afetch-2.2.0
Date: Sun, 09 Jan 2022 00:58:48 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34955@inbox.vuxu.org> (raw)

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

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

https://github.com/kawaiiamber/void-packages afetch
https://github.com/void-linux/void-packages/pull/34955

New package: afetch-2.2.0
<!-- Uncomment relevant sections and delete options which are not applicable -->

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

#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): **YES**

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration)
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->

#### Local build testing
- I built this PR locally for my native architecture, (x86_64-MUSL-LIBC)

Old PR is [closed](https://github.com/void-linux/void-packages/pull/30632).

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

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

From 01749765165329f4a51c72bd5d711cdc13d971d2 Mon Sep 17 00:00:00 2001
From: KawaiiAmber <japaneselearning101@gmail.com>
Date: Sat, 8 Jan 2022 16:58:52 -0700
Subject: [PATCH] New package: afetch-2.2.0

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

diff --git a/srcpkgs/afetch/template b/srcpkgs/afetch/template
new file mode 100644
index 000000000000..7adbaa1d2e62
--- /dev/null
+++ b/srcpkgs/afetch/template
@@ -0,0 +1,11 @@
+# Template file for 'afetch'
+pkgname=afetch
+version=2.2.0
+revision=1
+build_style=gnu-makefile
+short_desc="Simple system info written in C"
+maintainer="KawaiiAmber <japaneselearning101@gmail.com>"
+license="GPL-3.0-only"
+homepage="https://github.com/13-CF/afetch"
+distfiles="${homepage}/archive/refs/tags/V${version}.tar.gz"
+checksum=e1f4630b2f8aea0edb76676afbfba9b92c819c6df5da68eb5b89da9c330e2fcd

             reply	other threads:[~2022-01-08 23:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08 23:58 kawaiiamber [this message]
2022-01-09  0:22 ` [PR PATCH] [Updated] " kawaiiamber
2022-01-09  0:23 ` kawaiiamber
2022-01-09  0:26 ` kawaiiamber
2022-04-10  2:05 ` github-actions
2022-04-14 19:50 ` Chocimier
2022-04-14 19:50 ` [PR PATCH] [Closed]: " Chocimier

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-34955@inbox.vuxu.org \
    --to=kawaiiamber@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).