Github messages for voidlinux
 help / color / mirror / Atom feed
From: anddam <anddam@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] Add new package walk
Date: Wed, 27 Jan 2021 22:14:40 +0100	[thread overview]
Message-ID: <20210127211440.Fkbov9T4Dpr4gK45O5QujUaLihrfjsYHs-GaA6Zv6GQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28273@inbox.vuxu.org>

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

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

https://github.com/anddam/void-packages feature-new-package-walk
https://github.com/void-linux/void-packages/pull/28273

Add new package walk
<!-- 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?
- [x] 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, (ARCH-LIBC)
- [ ] 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/28273.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-feature-new-package-walk-28273.patch --]
[-- Type: text/x-diff, Size: 1705 bytes --]

From 31ef100bd88f85d7ae39a4ef68df4a4b1071cc8c Mon Sep 17 00:00:00 2001
From: Andrea D'Amore <a@d-amo.re>
Date: Tue, 27 Oct 2020 10:18:43 +0100
Subject: [PATCH 1/2] Add new package walk

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

diff --git a/srcpkgs/walk/template b/srcpkgs/walk/template
new file mode 100644
index 00000000000..0426104c230
--- /dev/null
+++ b/srcpkgs/walk/template
@@ -0,0 +1,26 @@
+# Template file for 'walk'
+pkgname=walk
+version=20190920
+revision=1
+_commit=70f7a8c104acf109ae810a9b34eb8e8b92b4d27d
+build_style="gnu-makefile"
+wrksrc="${pkgname}-${_commit}"
+short_desc="walk and sor utility, collectively replacing find"
+maintainer="orphaned"
+license="Apache-2.0"
+homepage="https://github.com/google/walk"
+distfiles="https://github.com/google/walk/archive/${_commit}.tar.gz"
+checksum=fce16683d757605a11284586794627a4352ec62718c59093a02f56b39896a1cd
+
+do_build() {
+    make
+}
+
+do_install() {
+    vinstall sor 0755 usr/bin/
+    vinstall walk 0755 usr/bin/
+    vman sor.1
+    vman walk.1
+    vdoc README.md
+	vlicense LICENSE
+}

From 75301a791352a014669d84e207b6f1646585f595 Mon Sep 17 00:00:00 2001
From: Andrea D'Amore <a@d-amo.re>
Date: Wed, 27 Jan 2021 22:13:07 +0100
Subject: [PATCH 2/2] Avoid installing license file per travis linting in CI

---
 srcpkgs/walk/template | 1 -
 1 file changed, 1 deletion(-)

diff --git a/srcpkgs/walk/template b/srcpkgs/walk/template
index 0426104c230..a005372d047 100644
--- a/srcpkgs/walk/template
+++ b/srcpkgs/walk/template
@@ -22,5 +22,4 @@ do_install() {
     vman sor.1
     vman walk.1
     vdoc README.md
-	vlicense LICENSE
 }

  reply	other threads:[~2021-01-27 21:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-27 21:10 [PR PATCH] " anddam
2021-01-27 21:14 ` anddam [this message]
2021-01-27 21:15 ` [PR REVIEW] " abenson
2021-01-27 21:15 ` abenson
2021-01-27 21:15 ` abenson
2021-01-27 21:16 ` abenson
2021-01-27 21:17 ` abenson
2021-01-27 21:27 ` [PR PATCH] [Updated] " anddam
2021-01-27 21:27 ` [PR REVIEW] " anddam
2021-01-27 21:28 ` anddam
2021-01-27 21:29 ` anddam
2021-01-27 21:34 ` abenson
2021-01-27 21:38 ` abenson
2021-01-27 21:40 ` [PR REVIEW] " anddam
2021-01-27 21:40 ` anddam
2021-01-27 21:42 ` [PR PATCH] [Updated] " anddam
2021-01-27 21:45 ` anddam
2021-01-27 21:46 ` [PR REVIEW] " anddam
2021-01-27 22:06 ` ericonr
2021-01-27 22:07 ` ericonr
2021-01-27 22:13 ` [PR PATCH] [Updated] " anddam
2021-02-15 23:56 ` anddam
2021-02-15 23:58 ` [PR REVIEW] " anddam
2021-02-15 23:58 ` anddam
2022-05-02  2:16 ` github-actions
2022-05-17  2:14 ` [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=20210127211440.Fkbov9T4Dpr4gK45O5QujUaLihrfjsYHs-GaA6Zv6GQ@z \
    --to=anddam@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).