From: ju-ef <ju-ef@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] Rocket.Chat-Desktop: update to 3.9.11
Date: Fri, 29 Dec 2023 15:09:15 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-47975@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
There is a new pull request by ju-ef against master on the void-packages repository
https://github.com/ju-ef/void-packages rocket.chat-desktop
https://github.com/void-linux/void-packages/pull/47975
Rocket.Chat-Desktop: update to 3.9.11
#### Testing the changes
- I tested the changes in this PR: **briefly**
#### 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/47975.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-rocket.chat-desktop-47975.patch --]
[-- Type: text/x-diff, Size: 1914 bytes --]
From b59c9e2e875e92f9d006c5e03cf5b5a65c42d294 Mon Sep 17 00:00:00 2001
From: juef <juef@juef.net>
Date: Fri, 29 Dec 2023 16:02:36 +0200
Subject: [PATCH] Rocket.Chat-Desktop: update to 3.9.11
---
srcpkgs/Rocket.Chat-Desktop/template | 23 +++++------------------
1 file changed, 5 insertions(+), 18 deletions(-)
diff --git a/srcpkgs/Rocket.Chat-Desktop/template b/srcpkgs/Rocket.Chat-Desktop/template
index d7ecb67b7473f..6e75899df44d2 100644
--- a/srcpkgs/Rocket.Chat-Desktop/template
+++ b/srcpkgs/Rocket.Chat-Desktop/template
@@ -1,8 +1,8 @@
# Template file for 'Rocket.Chat-Desktop'
pkgname=Rocket.Chat-Desktop
-version=3.8.7
-revision=2
-_electron_ver=19
+version=3.9.11
+revision=1
+_electron_ver=24
hostmakedepends="yarn nodejs python3 pkg-config app-builder"
makedepends="electron${_electron_ver} libvips-devel"
depends="electron${_electron_ver}"
@@ -11,26 +11,13 @@ maintainer="John <me@johnnynator.dev>"
license="MIT"
homepage="https://rocket.chat/"
distfiles="https://github.com/RocketChat/Rocket.Chat.Electron/archive/${version}.tar.gz"
-checksum=ac46390b4ae9e193efa92d5a38947c99fa94140604302b6850b9167e49eea453
+checksum=936525dd74dcc9050bfb91ecf4ce80d6a5be38de8bfbb9b05f2faac7b3a9a580
export USE_SYSTEM_APP_BUILDER=true
-do_configure() {
- # we can't make electron skip binary download as that fails in do_build
- # so instead, force a bogus architecture so it downloads its binary
- # artifact, it will use the system one later anyway
- # but this appears to fail on i686, so don't override there
- local carch=x64
- case "$XBPS_TARGET_MACHINE" in
- i686*) carch=ia32 ;;
- esac
- npm_config_arch=$carch \
- yarn upgrade electron@"$(</usr/lib/electron${_electron_ver}/version)" \
- --non-interactive
-}
-
do_build() {
export NODE_ENV=production
+ yarn install
yarn build
yarn run electron-builder --linux --x64 --dir \
-c.electronDist=/usr/lib/electron${_electron_ver} \
next reply other threads:[~2023-12-29 14:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-29 14:09 ju-ef [this message]
2023-12-30 15:01 ` ju-ef
2024-03-30 1:43 ` github-actions
2024-04-14 1:59 ` [PR PATCH] [Closed]: " github-actions
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-47975@inbox.vuxu.org \
--to=ju-ef@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).