Github messages for voidlinux
 help / color / mirror / Atom feed
From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] hplip: update to 3.22.10. + New package: hplip-plugin 3.22.10
Date: Wed, 28 Dec 2022 17:36:17 +0100	[thread overview]
Message-ID: <20221228163617.21_OOkoQZAEYoG70DfH_EEQHtyEZqbmTGI7Rl0IBNGk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-40434@inbox.vuxu.org>

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

New review comment by ahesford on void-packages repository

https://github.com/void-linux/void-packages/pull/40434#discussion_r1058464119

Comment:
Use `vinstall`, that's what it was made for. Not only does it make directories as needed, but we can remove the group-write bit from all of these files.

Also, I don't see why we need the original `-${_arch}` in the names if you're just going to symlink these to generic names (presumably `hplip` expects to find generic names anyway), so just drop the symlink and install the files with their generic names in the first place. (If that doesn't work, just drop the fourth argument from `vinstall` and keep your `find` loop.)

```suggestion
	local _arch _f

	case "$XBPS_TARGET_MACHINE" in
		i686) _arch='x86_32' ;;
		x86_64) _arch='x86_64' ;;
		armv[67]l) _arch='arm32' ;;
		aarch64) _arch='arm64' ;;
	esac

	vinstall plugin.spec 0644 usr/share/hplip

	for _f in hp_laserjet_*.fw.gz; do
		vinstall "${_f}" 0644 usr/share/hplip/data/firmware
	done

	vinstall "fax_marvell-${_arch}.so" 0755 \
		usr/share/hplip/fax/plugins fax_marvell.so

	vinstall "hbpl1-${_arch}.so" 0755 \
		usr/share/hplip/prnt/plugins hbpl1.so

	vinstall "lj-${_arch}.so" 0755 \
		usr/share/hplip/prnt/plugins lj.so

	for _f in bb_*-"${_arch}.so"; do
		vinstall "${_f}" 0755 \
			usr/share/hplip/scan/plugins "${_f/-${_arch}}"
	done

	vlicense license.txt

	cat <<-EOF > hplip.state
		[plugin]
		installed = 1
		eula = 1
		version = ${version}
		EOF

	vinstall hplip.state 0644 var/lib/hp
```

  parent reply	other threads:[~2022-12-28 16:36 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-10  7:19 [PR PATCH] hplip: update to 3.22.10 dataCobra
2022-11-10 10:11 ` [PR REVIEW] " paper42
2022-11-10 10:38 ` dataCobra
2022-11-10 11:46 ` biopsin
2022-11-11  8:05 ` [PR PATCH] [Updated] " dataCobra
2022-11-11  8:09 ` [PR REVIEW] " dataCobra
2022-11-16 14:07 ` [PR PATCH] [Updated] " dataCobra
2022-11-16 14:26 ` [PR PATCH] [Updated] hplip: update to 3.22.10. + New package: hplip-plugin 3.22.10 dataCobra
2022-11-16 14:27 ` dataCobra
2022-11-16 15:21 ` ahesford
2022-11-16 15:40 ` dataCobra
2022-11-16 15:58 ` biopsin
2022-11-16 16:06 ` ahesford
2022-11-17 12:25 ` biopsin
2022-11-17 12:54 ` biopsin
2022-11-17 13:03 ` paper42
2022-11-17 13:03 ` paper42
2022-11-17 13:17 ` biopsin
2022-11-17 13:23 ` biopsin
2022-11-17 18:57 ` ahesford
2022-11-18 10:36 ` dataCobra
2022-12-18 11:40 ` [PR PATCH] [Updated] " dataCobra
2022-12-18 11:49 ` dataCobra
2022-12-18 12:20 ` dataCobra
2022-12-18 13:52 ` biopsin
2022-12-24 11:15 ` biopsin
2022-12-24 11:15 ` biopsin
2022-12-24 23:27 ` [PR REVIEW] " paper42
2022-12-24 23:27 ` paper42
2022-12-25  1:29 ` ahesford
2022-12-28  7:12 ` [PR PATCH] [Updated] " dataCobra
2022-12-28  8:31 ` [PR REVIEW] " dataCobra
2022-12-28  8:32 ` [PR PATCH] [Updated] " dataCobra
2022-12-28 10:19 ` [PR REVIEW] " dataCobra
2022-12-28 16:05 ` biopsin
2022-12-28 16:36 ` ahesford
2022-12-28 16:36 ` ahesford
2022-12-28 16:36 ` ahesford [this message]
2023-01-04  7:44 ` [PR PATCH] [Updated] " dataCobra
2023-01-13  9:08 ` biopsin
2023-01-13 11:30 ` [PR PATCH] [Merged]: " ahesford
2023-01-13 11:46 ` ahesford

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=20221228163617.21_OOkoQZAEYoG70DfH_EEQHtyEZqbmTGI7Rl0IBNGk@z \
    --to=ahesford@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).