From: fosslinux <fosslinux@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] protonmail-bridge: build from source
Date: Wed, 17 Feb 2021 08:17:40 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28810@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
New issue by fosslinux on void-packages repository
https://github.com/void-linux/void-packages/issues/28810
Description:
protonmail-bridge has source code available now, however this has not always been the case, so it currently uses a downloaded binary. (https://github.com/ProtonMail/proton-bridge).
We should change that; however, `protonmail-bridge`'s build process is quite complex, and it is not very easy to build it from source.
next reply other threads:[~2021-02-17 7:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 7:17 fosslinux [this message]
2022-05-04 2:15 ` github-actions
2022-05-19 2:15 ` [ISSUE] [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-28810@inbox.vuxu.org \
--to=fosslinux@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).