Github messages for voidlinux
 help / color / mirror / Atom feed
From: b-l-a-i-n-e <b-l-a-i-n-e@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: 1password-8.4.1
Date: Mon, 13 Dec 2021 19:54:59 +0100	[thread overview]
Message-ID: <20211213185459.H1ivD45P5wFQ3_AOlGABMJ23n4CyF4zoiW8Ue3BkdxY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34427@inbox.vuxu.org>

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

There is an updated pull request by b-l-a-i-n-e against master on the void-packages repository

https://github.com/b-l-a-i-n-e/void-packages 1password
https://github.com/void-linux/void-packages/pull/34427

New package: 1password-8.4.1
#### Testing the changes
- I tested the changes in this PR: YES

#### New package
- This new package conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements): YES

#### Local build testing
- I built this PR locally for my native architecture, (x86_64-GLIBC)


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

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-1password-34427.patch --]
[-- Type: text/x-diff, Size: 3398 bytes --]

From c2e607147190ecbdb9b950357127afa021d389f1 Mon Sep 17 00:00:00 2001
From: b-l-a-i-n-e <blaine.gilbreth@gmail.com>
Date: Wed, 8 Dec 2021 01:35:46 -0800
Subject: [PATCH] New package: 1password-8.4.1

---
 srcpkgs/1password/INSTALL         | 11 ++++++
 srcpkgs/1password/files/1password |  2 ++
 srcpkgs/1password/template        | 56 +++++++++++++++++++++++++++++++
 3 files changed, 69 insertions(+)
 create mode 100644 srcpkgs/1password/INSTALL
 create mode 100644 srcpkgs/1password/files/1password
 create mode 100644 srcpkgs/1password/template

diff --git a/srcpkgs/1password/INSTALL b/srcpkgs/1password/INSTALL
new file mode 100644
index 000000000000..c4ec5e9b3720
--- /dev/null
+++ b/srcpkgs/1password/INSTALL
@@ -0,0 +1,11 @@
+# INSTALL
+case "${ACTION}" in
+post)
+	chmod 4755 opt/1Password/chrome-sandbox
+	chown :onepassword opt/1Password/1Password-KeyringHelper
+	chmod u+s opt/1Password/1Password-KeyringHelper
+	chmod g+s opt/1Password/1Password-KeyringHelper
+	chown :onepassword opt/1Password/1Password-BrowserSupport
+	chmod g+s opt/1Password/1Password-BrowserSupport
+	;;
+esac
diff --git a/srcpkgs/1password/files/1password b/srcpkgs/1password/files/1password
new file mode 100644
index 000000000000..c1c521260437
--- /dev/null
+++ b/srcpkgs/1password/files/1password
@@ -0,0 +1,2 @@
+#!/bin/sh
+exec /opt/1Password/1password "$@"
diff --git a/srcpkgs/1password/template b/srcpkgs/1password/template
new file mode 100644
index 000000000000..2a3ea9570958
--- /dev/null
+++ b/srcpkgs/1password/template
@@ -0,0 +1,56 @@
+# Template file for '1password'
+pkgname=1password
+version=8.4.1
+revision=1
+_1passworddir="1password-${version}.x64"
+_filename="${_1passworddir}.tar.gz"
+archs="x86_64"
+create_wrksrc=yes
+hostmakedepends="curl w3m libcurl gnupg"
+short_desc="Password manager"
+maintainer="b-l-a-i-n-e <blaine.gilbreth@gmail.com>"
+license="custom:Proprietary"
+homepage="https://www.1password.com"
+distfiles="https://downloads.1password.com/linux/tar/stable/x86_64/${_filename}"
+checksum=f5c2468127c363b3a3d2fa5857b6ff0979eeaf1485c1afb114b3929c1fc4a7df
+system_groups="onepassword"
+_license_checksum=b8f6ff9297488416f3d8063a151109ed5e8a2df6fa546856a4beaa715cbc0fda
+_gpg_key=3FEF9748469ADBE15DA7CA80AC2D62742012EA22
+repository=nonfree
+restricted=yes
+nostrip=yes
+noshlibprovides=yes
+
+post_fetch() {
+	# verify gpg key
+	curl -L "${distfiles}.sig" > "${_filename}.sig"
+	if ! gpg --recv-keys "${_gpg_key}"; then
+		msg_error "Incorrect gpg key: ${_gpg_key}\n"
+	fi
+	if ! gpg --verify "${_filename}.sig" "${_filename}"; then
+		msg_error "gpg verify failed\n"
+	fi
+
+	# verify EULA
+	curl -L https://1password.com/legal/terms-of-service/ |
+		w3m -dump -I utf-8 -T text/html |
+		sed -n '/Service Agreement for 1Password/,/We clarified what happens if we part ways./p' > EULA
+	filesum="$(xbps-digest EULA)"
+	if [ "$filesum" != "$_license_checksum" ]; then
+		msg_error "SHA256 mismatch for EULA:\n$filesum\n"
+	fi
+}
+
+post_extract() {
+	# copy the verified EULA
+	cp "${XBPS_SRCDISTDIR}/${pkgname}-${version}/EULA" "${wrksrc}"
+}
+
+do_install() {
+	vmkdir opt/1Password
+	vcopy "${_1passworddir}/*" opt/1Password
+	vinstall "${_1passworddir}/com.1password.1Password.policy" 644 usr/share/polkit-1/actions/
+	vinstall "${_1passworddir}/resources/custom_allowed_browsers" 644 usr/share/doc/1password/examples/
+	vbin "${FILESDIR}/1password"
+	vlicense EULA
+}

  parent reply	other threads:[~2021-12-13 18:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08  9:46 [PR PATCH] " b-l-a-i-n-e
2021-12-08  9:48 ` b-l-a-i-n-e
2021-12-08  9:49 ` b-l-a-i-n-e
2021-12-08  9:50 ` b-l-a-i-n-e
2021-12-08 17:31 ` Chocimier
2021-12-08 22:11 ` [PR PATCH] [Updated] " b-l-a-i-n-e
2021-12-08 22:18 ` b-l-a-i-n-e
2021-12-08 22:23 ` b-l-a-i-n-e
2021-12-08 23:15 ` b-l-a-i-n-e
2021-12-09 17:28 ` b-l-a-i-n-e
2021-12-13 18:54 ` b-l-a-i-n-e [this message]
2021-12-13 19:36 ` [PR PATCH] [Updated] " Chocimier
2021-12-13 19:37 ` Chocimier
2021-12-13 19:38 ` Chocimier
2021-12-15 20:09 ` [PR PATCH] [Merged]: " Chocimier

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=20211213185459.H1ivD45P5wFQ3_AOlGABMJ23n4CyF4zoiW8Ue3BkdxY@z \
    --to=b-l-a-i-n-e@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).