From 92d7391de578e4a11066fee1c639d4371905b93a Mon Sep 17 00:00:00 2001
From: Max Rees <maxcrees@me.com>
Date: Sat, 20 Jul 2019 22:02:48 -0400
Subject: abuild: use command(1) portably

According to POSIX, the "command -v" form of command(1) accepts only a
single argument (command_name). Some shells will check additional
arguments, but not dash.
---
 abuild.in | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/abuild.in b/abuild.in
index 12c875c..39276b8 100644
--- a/abuild.in
+++ b/abuild.in
@@ -1465,7 +1465,7 @@ human_size() {
 
 create_apks() {
 	local file= dir= name= ver= apk= datadir= size=
-	local gzip=$(command -v pigz gzip | head -1)
+	local gzip=$(command -v pigz || echo gzip)
 	getpkgver || return 1
 	if ! options_has "!tracedeps"; then
 		for file in "$pkgbasedir"/.control.*/.PKGINFO; do
@@ -1598,7 +1598,7 @@ check() {
 
 # predefined splitfunc doc
 default_doc() {
-	local gzip=$(command -v pigz gzip | head -1)
+	local gzip=$(command -v pigz || echo gzip)
 	depends="$depends_doc"
 	pkgdesc="$pkgdesc (documentation)"
 	install_if="docs $pkgname=$pkgver-r$pkgrel"
-- 
cgit v1.2.3-60-g2f50