From: Christian Hesse <mail@eworm.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: binary module for arch?
Date: Tue, 1 Jan 2019 21:50:07 +0100 [thread overview]
Message-ID: <20190101215007.15f15e05@leda> (raw)
In-Reply-To: <CAHmME9pvcrTnbzSvAS3Q1CbPRdZMctuyBmuCyxX0wa_k+A-0tw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 698 bytes --]
"Jason A. Donenfeld" <Jason@zx2c4.com> on Mon, 2018/12/31 01:58:
> Hey Christian,
>
> I noticed there are now two distro-built packages for wireguard for
> arch -- wireguard-lts and wireguard-arch. These seem probably more
> convenient for most people than the dkms one. What would you recommend
> in terms of updating wireguard.com/install/ ? And do you plan on
> depreciating the dkms one at some point, or do you think it will
> remain useful for certain users?
Hey Jason,
some people gave their legit reasons to keep wireguard-dkms. I have to add
another one: It is a build-dependency for the binary modules packages. So it
will stay definitely. ;)
--
Best regards,
Chris
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-01-02 7:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 0:58 binary module for arch? Jason A. Donenfeld
2018-12-31 1:48 ` Davide Depau
2018-12-31 16:11 ` John
2019-01-01 12:44 ` Jordan Glover
2019-01-01 20:54 ` Christian Hesse
2019-01-01 20:50 ` Christian Hesse [this message]
2019-01-02 0:22 ` Jason A. Donenfeld
2019-01-02 7:57 ` Christian Hesse
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=20190101215007.15f15e05@leda \
--to=mail@eworm.de \
--cc=Jason@zx2c4.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.