From: Christian Hesse <list@eworm.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Christian Hesse <mail@eworm.de>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: binary module for arch?
Date: Wed, 2 Jan 2019 08:57:42 +0100 [thread overview]
Message-ID: <20190102085742.6184fe45@leda> (raw)
In-Reply-To: <CAHmME9puWpU-acT_sAE4qvg6ENAkvwpxMEU7czYUwtdMUQPLVg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1355 bytes --]
"Jason A. Donenfeld" <Jason@zx2c4.com> on Wed, 2019/01/02 01:22:
> Hi Christian,
>
> On Tue, Jan 1, 2019 at 9:50 PM Christian Hesse <mail@eworm.de> wrote:
> >
> > "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?
> > 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. ;)
>
> Makes sense. I was mostly wondering about that first question though:
> what would you recommend I put on wireguard.com/install/ for Arch
> users?
I sent another mail to the other branch of the thread. Did that answer your
question?
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-01-02 7:58 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
2019-01-02 0:22 ` Jason A. Donenfeld
2019-01-02 7:57 ` Christian Hesse [this message]
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=20190102085742.6184fe45@leda \
--to=list@eworm.de \
--cc=Jason@zx2c4.com \
--cc=mail@eworm.de \
--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