From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [Package request] Electron 17+
Date: Sun, 24 Apr 2022 21:15:22 +0200 [thread overview]
Message-ID: <20220424191522.JYgMAKWeOzHrgT6KIL61ovQbAcyOui_qMFuLyNCMfYA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36451@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 913 bytes --]
New comment by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/issues/36451#issuecomment-1107901019
Comment:
Here's what I previously tried to come up with for `electron18`, someone feel free to continue work based on this: [electron18.tar.gz](https://github.com/void-linux/void-packages/files/8550350/electron18.tar.gz)
All the patches were modified (didn't apply anymore), updated (e.g. all chromium patches against `srcpkgs/chromium`) and dropped (if already applied upstream) as needed.
My system doesn't have nearly enough resources for me to keep working on that quickly enough as even extraction takes about 5 minutes each time and then I'd essentially have to wait for chromium to build and fix any and all issues that may arise during that. Besides I already have plenty of other projects which I'd rather work on than build chromium over and over again ;)
next prev parent reply other threads:[~2022-04-24 19:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 9:11 [ISSUE] " atk
2022-04-10 11:27 ` RicArch97
2022-04-24 8:11 ` cevdetardaharan
2022-04-24 19:15 ` JamiKettunen [this message]
2022-06-10 12:16 ` JamiKettunen
2022-06-10 19:33 ` atk
2022-07-29 14:47 ` JamiKettunen
2022-07-29 14:55 ` [ISSUE] [CLOSED] " 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=20220424191522.JYgMAKWeOzHrgT6KIL61ovQbAcyOui_qMFuLyNCMfYA@z \
--to=jamikettunen@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).