From: JamiKettunen <JamiKettunen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: waydroid-1.2.1
Date: Wed, 10 Aug 2022 00:22:35 +0200 [thread overview]
Message-ID: <20220809222235.q1amfMjyCl9nvCaRP_mALr04TtHIV4jK9qyHyGEn1-A@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-37611@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1048 bytes --]
New comment by JamiKettunen on void-packages repository
https://github.com/void-linux/void-packages/pull/37611#issuecomment-1209944331
Comment:
@sgn Did you already have `nftables` installed from before trying Waydroid? All `LXC_USE_NFT="true"` does is it allows the network setup script to also potentially use `nftables` instead of `iptables` default (see the [`use_nft()` function](https://github.com/waydroid/waydroid/blob/main/data/scripts/waydroid-net.sh#L41-L43)) which I completely agree we should set.
I could just force installation of `nftables` (add it to `waydroid` depends) as well if you think that's better to make sure everyone uses that instead of potentially `iptables` for Waydroid network configuration.
Btw [the README.voidlinux](https://github.com/JamiKettunen/void-packages/blob/waydroid/srcpkgs/waydroid/files/README.voidlinux) (in this PR) has a bunch of content already, if I don't just add dependency on `nftables` I would've added a note it is another way to setup the networking instead of `iptables` default.
next prev parent reply other threads:[~2022-08-09 22:22 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 0:51 [PR PATCH] " JamiKettunen
2022-06-19 1:25 ` CameronNemo
2022-06-19 1:42 ` JamiKettunen
2022-06-19 6:35 ` CameronNemo
2022-06-19 6:36 ` CameronNemo
2022-06-19 8:19 ` Johnnynator
2022-06-19 12:45 ` JamiKettunen
2022-06-19 19:25 ` JamiKettunen
2022-06-19 19:36 ` JamiKettunen
2022-06-20 16:40 ` [PR PATCH] [Updated] " JamiKettunen
2022-06-20 19:12 ` JamiKettunen
2022-06-22 15:36 ` JamiKettunen
2022-06-23 18:36 ` JamiKettunen
2022-06-24 21:13 ` JamiKettunen
2022-06-25 20:40 ` JamiKettunen
2022-07-04 22:28 ` JamiKettunen
2022-07-07 0:04 ` JamiKettunen
2022-07-14 0:36 ` JamiKettunen
2022-07-19 15:00 ` JamiKettunen
2022-07-21 12:48 ` JamiKettunen
2022-07-24 14:23 ` sgn
2022-07-24 15:25 ` [PR PATCH] [Updated] " JamiKettunen
2022-07-29 16:43 ` sgn
2022-07-29 18:21 ` JamiKettunen
2022-07-29 18:26 ` [PR PATCH] [Updated] " JamiKettunen
2022-07-29 18:41 ` CameronNemo
2022-07-30 0:15 ` sgn
2022-07-30 0:34 ` sgn
2022-08-09 10:58 ` JamiKettunen
2022-08-09 10:59 ` JamiKettunen
2022-08-09 11:01 ` JamiKettunen
2022-08-09 11:01 ` sgn
2022-08-09 11:18 ` JamiKettunen
2022-08-09 11:35 ` JamiKettunen
2022-08-09 14:08 ` sgn
2022-08-09 15:20 ` JamiKettunen
2022-08-09 15:23 ` JamiKettunen
2022-08-09 15:32 ` sgn
2022-08-09 22:12 ` JamiKettunen
2022-08-09 22:21 ` JamiKettunen
2022-08-09 22:22 ` JamiKettunen [this message]
2022-08-09 22:23 ` JamiKettunen
2022-08-09 23:17 ` CameronNemo
2022-08-10 0:18 ` sgn
2022-08-10 12:02 ` JamiKettunen
2022-08-11 2:34 ` CameronNemo
2022-08-12 19:31 ` [PR PATCH] [Updated] " JamiKettunen
2022-08-12 22:00 ` JamiKettunen
2022-08-13 18:11 ` New package: waydroid-1.3.0 jcgruenhage
2022-08-13 18:19 ` JamiKettunen
2022-08-13 18:46 ` jcgruenhage
2022-08-13 19:08 ` JamiKettunen
2022-08-21 10:36 ` JamiKettunen
2022-08-21 11:12 ` [PR PATCH] [Merged]: " sgn
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=20220809222235.q1amfMjyCl9nvCaRP_mALr04TtHIV4jK9qyHyGEn1-A@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).