From: mikoxyz <mikoxyz@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Signal-Desktop for i686
Date: Sat, 20 Nov 2021 14:15:28 +0100 [thread overview]
Message-ID: <20211120131528.ifWy6hUTYIDf862c8IaMd721vdzW3hNk1yk1kaCef1o@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34126@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]
New comment by mikoxyz on void-packages repository
https://github.com/void-linux/void-packages/issues/34126#issuecomment-974648966
Comment:
> > > And so what? Electron 32 bit package exists in npm repository. Latest version.
> >
> >
> > a) We don't use npm, so that's irrelevant.
>
> The Signal-Desktop packages does use the npm repos.
Was primarily referring to the Electron package not using npm, but yeah, that's a miss on my end. Sorry about that.
> > b) "So what"? 32-bit builds are still not officially supported, and I doubt someone here wants to maintain a psuedo-fork of Electron and Signal. Do it yourself, if you're so inclined.
>
> No need to fork electron, they still support x86, that blog post doesn't representet status quo. I can't say anything about signal and what might or might not be broken with 32bit builds. These two issues are mainly about their packaging work and not about third party packaging.
Oh, really? Another miss on my end, then; was going completely after the blog post. Sorry ^^;
next prev parent reply other threads:[~2021-11-20 13:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 3:30 [ISSUE] " artenaki
2021-11-19 16:15 ` mikoxyz
2021-11-20 1:23 ` artenaki
2021-11-20 10:29 ` mikoxyz
2021-11-20 12:20 ` Johnnynator
2021-11-20 12:25 ` ericonr
2021-11-20 13:15 ` mikoxyz [this message]
2021-11-20 16:38 ` Johnnynator
2021-11-20 16:38 ` [ISSUE] [CLOSED] " Johnnynator
2021-11-21 9:22 ` artenaki
2021-11-21 9:33 ` artenaki
2021-11-21 9:35 ` artenaki
2022-02-09 1:32 ` artenaki
2022-02-09 1:37 ` artenaki
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=20211120131528.ifWy6hUTYIDf862c8IaMd721vdzW3hNk1yk1kaCef1o@z \
--to=mikoxyz@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).