From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] unar: fix bash completions path
Date: Fri, 10 May 2019 07:15:12 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-11605@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 318 bytes --]
There is a new pull request by bobertlo against master on the void-packages repository
https://github.com/bobertlo/void-packages unarfix
https://github.com/void-linux/void-packages/pull/11605
unar: fix bash completions path
A patch file from https://github.com/void-linux/void-packages/pull/11605.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-unarfix-11605.patch --]
[-- Type: application/text/x-diff, Size: 897 bytes --]
From 93c4147ca74d83788dd340393a326e054a4bd4e5 Mon Sep 17 00:00:00 2001
From: Robert Lowry <bobertlo@gmail.com>
Date: Fri, 10 May 2019 00:13:49 -0500
Subject: [PATCH] unar: fix bash completions path
---
srcpkgs/unar/template | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/srcpkgs/unar/template b/srcpkgs/unar/template
index fc929e71cf0..735272198b1 100644
--- a/srcpkgs/unar/template
+++ b/srcpkgs/unar/template
@@ -1,7 +1,7 @@
# Template file for 'unar'
pkgname=unar
version=1.10.5
-revision=1
+revision=2
archs="~*-musl" # regexec incompatible
build_wrksrc="XADMaster"
build_style=gnu-makefile
@@ -26,6 +26,6 @@ do_install() {
for x in unar lsar; do
vbin "$x"
vman "Extra/${x}.1"
- vinstall "Extra/${x}.bash_completion" 644 usr/share/bash-completions "$x"
+ vinstall "Extra/${x}.bash_completion" 644 usr/share/bash-completion/completions "$x"
done
}
reply other threads:[~2019-05-10 5:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-11605@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--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).