From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: wireguard@bulletin.elitemail.org
Cc: wireguard@lists.zx2c4.com
Subject: Re: APK outside of Play Store?
Date: Sun, 2 Oct 2022 10:56:59 +0200 [thread overview]
Message-ID: <YzlSW9qQ+c/0tB5A@zx2c4.com> (raw)
In-Reply-To: <17e101ab-1434-43cb-af2c-437623bfecbf@app.fastmail.com>
On Sun, Oct 02, 2022 at 03:03:51AM +0000, wireguard@bulletin.elitemail.org wrote:
> F-Droid builds on EOL Debian Stretch using an outdated toolchain and
> dependencies is not the way. An official build on a supported non-EOL
> OS signed by first-party development is.
Is there actually something inferior about the apks it generates? Yes,
we all know fdroid's infra is crumbly. But is there something wrong with
its output files? Can you point to something technically substantive
there? If you can identify a real technical problem, maybe there's
something I can do about that, by working with the fdroid developers, or
otherwise find some way. In the past, they've been able to bump NDK/SDK
revisions and whatnot without too much hassle. And these days, all is
usually fine so long as we stick with the non-beta releases (that is,
the open source releases) of AGP. But maybe now you've identified a new
problem? On the other hand, if you cannot identity a real technical
problem, I'm not sure I have much to comment on.
Jason
next prev parent reply other threads:[~2022-10-02 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 4:09 wireguard
2022-09-28 16:34 ` tempforever
2022-10-02 3:03 ` wireguard
2022-10-02 8:56 ` Jason A. Donenfeld [this message]
2023-05-15 23:43 ` Jason A. Donenfeld
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=YzlSW9qQ+c/0tB5A@zx2c4.com \
--to=jason@zx2c4.com \
--cc=wireguard@bulletin.elitemail.org \
--cc=wireguard@lists.zx2c4.com \
/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).