From: oreo639 <oreo639@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: vscode: update to 1.96.0
Date: Fri, 31 Jan 2025 12:07:25 +0100 [thread overview]
Message-ID: <20250131110725.90AC721732@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-51909@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]
New comment by oreo639 on void-packages repository
https://github.com/void-linux/void-packages/pull/51909#issuecomment-2626928013
Comment:
electron33 33.3.2 needs to be built with a specific chromium and npm release specified here: https://releases.electronjs.org/release/v33.3.2
I am currently building electron33 33.1.0 which is the first release including the patch, and the last electron33 series release that uses a non-extended stable verision of chromium. Extended stable versions of chromium don't have source tarballs available on the chromium-browser-official since they are primarily intended for commercial windows users.
Different distros handle that differently, looking at the void-packages history, we just don't update to those versions, Arch Linux uses git, Alpine and OpenSUSE generate electron tarballs with chromium sources included (since electron does not provide official tarballs), and FreeBSD hosts the chromium tarballs as github releases but has it split into multiple files due to upload limits. (most distros handle it by not shipping electron :p)
next prev parent reply other threads:[~2025-01-31 11:07 UTC|newest]
Thread overview: 79+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 10:42 [PR PATCH] vscode: update to 1.92.2 atk
2024-08-19 13:08 ` tranzystorekk
2024-08-20 6:46 ` tranzystorekk
2024-08-21 10:58 ` slymattz
2024-08-21 11:08 ` slymattz
2024-09-09 7:50 ` [PR PATCH] [Updated] " atk
2024-09-16 8:31 ` [PR PATCH] [Updated] vscode: update to 1.93.0 atk
2024-09-17 7:18 ` atk
2024-09-19 6:01 ` loukamb
2024-09-19 6:02 ` loukamb
2024-10-08 9:40 ` atk
2024-10-10 20:22 ` [PR PATCH] [Updated] " atk
2024-10-10 20:26 ` atk
2024-10-11 10:34 ` atk
2024-10-11 10:34 ` atk
2024-10-11 14:09 ` atk
2024-10-11 14:10 ` [PR PATCH] [Updated] " atk
2024-10-11 21:48 ` vscode: update to 1.94.2 Johnnynator
2024-10-12 7:34 ` atk
2024-10-12 16:57 ` Johnnynator
2024-10-15 5:27 ` atk
2024-10-15 14:36 ` Johnnynator
2024-10-18 21:44 ` atk
2024-10-30 11:07 ` Johnnynator
2024-10-31 7:52 ` atk
2024-10-31 7:52 ` atk
2024-10-31 17:28 ` atk
2024-10-31 18:09 ` Johnnynator
2024-11-01 8:28 ` atk
2024-11-01 9:06 ` atk
2024-11-01 11:36 ` atk
2024-11-01 11:36 ` [PR PATCH] [Updated] " atk
2024-11-04 11:07 ` atk
2024-11-04 11:08 ` atk
2024-11-04 11:10 ` atk
2024-11-05 8:53 ` [PR PATCH] [Updated] " atk
2024-11-12 9:40 ` vscode: update to 1.95.0 atk
2024-12-17 7:31 ` [PR PATCH] [Updated] " atk
2024-12-17 9:10 ` vscode: update to 1.96.0 atk
2025-01-07 14:26 ` Jipok
2025-01-07 15:09 ` atk
2025-01-11 18:04 ` marmeladema
2025-01-11 19:03 ` loukamb
2025-01-11 19:04 ` loukamb
2025-01-11 19:05 ` loukamb
2025-01-11 19:05 ` loukamb
2025-01-11 19:05 ` loukamb
2025-01-14 9:56 ` atk
2025-01-30 21:52 ` oreo639
2025-01-30 22:04 ` oreo639
2025-01-30 23:30 ` oreo639
2025-01-30 23:37 ` oreo639
2025-01-30 23:38 ` oreo639
2025-01-30 23:40 ` oreo639
2025-01-30 23:41 ` oreo639
2025-01-31 3:49 ` oreo639
2025-01-31 3:52 ` oreo639
2025-01-31 3:52 ` oreo639
2025-01-31 9:57 ` atk
2025-01-31 10:21 ` atk
2025-01-31 10:58 ` oreo639
2025-01-31 10:59 ` oreo639
2025-01-31 10:59 ` oreo639
2025-01-31 11:00 ` oreo639
2025-01-31 11:01 ` oreo639
2025-01-31 11:02 ` oreo639
2025-01-31 11:02 ` oreo639
2025-01-31 11:03 ` oreo639
2025-01-31 11:06 ` oreo639
2025-01-31 11:07 ` oreo639 [this message]
2025-01-31 11:26 ` oreo639
2025-01-31 16:12 ` Johnnynator
2025-02-01 9:56 ` oreo639
2025-02-01 10:10 ` oreo639
2025-02-03 9:03 ` [PR PATCH] [Updated] " atk
2025-02-03 9:04 ` atk
2025-02-03 9:04 ` atk
2025-02-05 7:26 ` vscode: update to 1.96.4 Johnnynator
2025-02-05 7:26 ` [PR PATCH] [Merged]: " Johnnynator
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=20250131110725.90AC721732@inbox.vuxu.org \
--to=oreo639@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).