From: Shen Red <firstname.lastname@example.org>
To: "email@example.com" <firstname.lastname@example.org>
Cc: "email@example.com" <firstname.lastname@example.org>
Subject: 回覆: Update wireguard installation instructions for RHEL7/8-Centos8Stream
Date: Fri, 15 Jul 2022 07:34:16 +0000 [thread overview]
Message-ID: <SYBP282MB04602F7E8D72EAA794403414F28B9@SYBP282MB0460.AUSP282.PROD.OUTLOOK.COM> (raw)
I understand your suggestion. Although I am not the administrator of the WireGuard website. But personally I don't even sure how to update the instruction properly for the current circumstances. As my understanding, the instructions from the WireGuard website aims to provide the best practices to install WireGuard. But unfortunately there is no best practice available for C8S for now, each method/workaround seems quite ugly to me.
Or should we just write down lengthy texts on the page to describe the situation? I think it will break the simplicity. Since the Stream is the beta/experimental build of RHEL. The user base is low and the demand of the instruction updating for that user base is also low. Consider that the CentOS Stream 8 does not actually mention in the instruction, only CentOS 8. I think we may leave the instruction in the current shape until we got some decisive solution to provide.
There is a bug #2103865 about the recent WireGuard breakage which I submitted to Red Hat Bugzilla, and I don't see any response yet.
reply other threads:[~2022-07-15 7:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).