Github messages for voidlinux
 help / color / mirror / Atom feed
From: FollieHiyuki <FollieHiyuki@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] exa: update to 0.10.0
Date: Sun, 04 Apr 2021 22:55:07 +0200	[thread overview]
Message-ID: <20210404205507.2wWpVUZXKvj9nMV1LWRYROCZzH0KW5x_63WYBrQXmoE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-30005@inbox.vuxu.org>

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

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

https://github.com/FollieHiyuki/void-packages exa-update
https://github.com/void-linux/void-packages/pull/30005

exa: update to 0.10.0
<!-- Mark items with [x] where applicable -->

#### General
- [ ] 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.)
- [ ] 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
-->

Upstream uses markdown for the man pages and convert them into plain text with `pandoc`. I don't know a convenient way to install them.
Another option is to pull the pre-compiled man pages from their release.


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

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

From d118911a184423f5676e7be7769192dd1c577397 Mon Sep 17 00:00:00 2001
From: FollieHiyuki <folliekazetani@protonmail.com>
Date: Sun, 4 Apr 2021 23:31:03 +0300
Subject: [PATCH] exa: update to 0.10.0; adopt

---
 srcpkgs/exa/template | 23 +++++++++++++----------
 1 file changed, 13 insertions(+), 10 deletions(-)

diff --git a/srcpkgs/exa/template b/srcpkgs/exa/template
index 5ea748de3627..b34c5126a90c 100644
--- a/srcpkgs/exa/template
+++ b/srcpkgs/exa/template
@@ -1,21 +1,24 @@
 # Template file for 'exa'
 pkgname=exa
-version=0.9.0
-revision=2
+version=0.10.0
+revision=1
 build_style=cargo
-hostmakedepends="pkg-config"
+hostmakedepends="pkg-config libgit2-devel"
 makedepends="libgit2-devel"
 short_desc="Modern replacement for ls"
-maintainer="Orphaned <orphan@voidlinux.org>"
+maintainer="FollieHiyuki <folliekazetani@protonmail.com>"
 license="MIT"
 homepage="https://the.exa.website/"
-distfiles="https://github.com/ogham/exa/archive/v${version}.tar.gz"
-checksum=@facbe3b234f403e1e1919f28f009f1733a0fbbbb11f0bc2ba89ac3eba11bc5e8
+distfiles="https://github.com/ogham/exa/archive/v${version}.tar.gz
+ https://github.com/ogham/exa/releases/download/v${version}/exa-accoutrements-v${version}.zip"
+checksum="27420f7b805941988399d63f388be4f6077eee94a505bf01c2fb0e7d15cbf78d
+ c1ab340af63e64bc3fd854c03f6161aa240a533e928688036a7d4544aecabc05"
 
 post_install() {
-	vman contrib/man/exa.1
-	vcompletion contrib/completions.bash bash
-	vcompletion contrib/completions.fish fish
-	vcompletion contrib/completions.zsh zsh
+	vman ../man/exa.1
+	vman ../man/exa_colors.5
+	vcompletion completions/completions.bash bash
+	vcompletion completions/completions.fish fish
+	vcompletion completions/completions.zsh zsh
 	vlicense LICENCE
 }

  reply	other threads:[~2021-04-04 20:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-04 20:35 [PR PATCH] " FollieHiyuki
2021-04-04 20:55 ` FollieHiyuki [this message]
2021-04-04 22:57 ` [PR REVIEW] " ericonr
2021-04-04 22:57 ` ericonr
2021-04-04 22:57 ` ericonr
2021-04-04 23:13 ` FollieHiyuki
2021-04-04 23:22 ` [PR PATCH] [Updated] " FollieHiyuki
2021-04-04 23:23 ` [PR REVIEW] " FollieHiyuki
2021-04-04 23:26 ` [PR PATCH] [Merged]: " ericonr

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=20210404205507.2wWpVUZXKvj9nMV1LWRYROCZzH0KW5x_63WYBrQXmoE@z \
    --to=folliehiyuki@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).