From: selfisekai <selfisekai@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] zulip-desktop: update to 5.10.0
Date: Sat, 16 Sep 2023 05:45:35 +0200 [thread overview]
Message-ID: <20230916034535.umfDVsTL5vrDSneqZONseCH9JKDd2cGaDpZHA3kvIRs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45242@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
New review comment by selfisekai on void-packages repository
https://github.com/void-linux/void-packages/pull/45242#discussion_r1327897592
Comment:
@classabbyamp fyi, I think upstream won't ever care, because for them this is auto-generated by electron-builder (which only does not generate it if you use `target=dir` :).
shameless plug alert: what I do in alpine is [electron_tasje](https://codeberg.org/selfisekai/electron_tasje), but that is so far broken in other noticeable ways (like requiring to remove dev deps before packing). also I think I can make just the desktop generator available in cli, if you want
next prev parent reply other threads:[~2023-09-16 3:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-25 9:26 [PR PATCH] " hervyqa
2023-07-25 11:16 ` [PR PATCH] [Updated] " hervyqa
2023-07-25 17:47 ` [PR REVIEW] " classabbyamp
2023-07-25 17:48 ` classabbyamp
2023-07-26 1:04 ` hervyqa
2023-07-26 1:08 ` [PR PATCH] [Updated] " hervyqa
2023-07-26 1:13 ` [PR REVIEW] " hervyqa
2023-08-04 12:02 ` hervyqa
2023-08-04 12:02 ` hervyqa
2023-09-16 3:45 ` selfisekai [this message]
2023-09-28 0:43 ` [PR PATCH] [Updated] " hervyqa
2023-09-30 14:54 ` [PR PATCH] [Updated] zulip-desktop: update to 5.10.2 hervyqa
2023-12-30 1:45 ` zulip-desktop: update to 5.10.3 github-actions
2024-01-13 1:46 ` [PR PATCH] [Closed]: " github-actions
2024-05-17 19:45 ` dkwo
2024-05-19 9:54 ` hervyqa
2024-05-20 21:00 ` dkwo
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=20230916034535.umfDVsTL5vrDSneqZONseCH9JKDd2cGaDpZHA3kvIRs@z \
--to=selfisekai@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).