From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
Egbert Verhage <egbert@eggiecode.org>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard in systemd-networkd
Date: Thu, 11 Jan 2018 16:02:30 +0100 [thread overview]
Message-ID: <CAHmME9q8_4Ln=OB7_NDTzE3JpTdf8Ae4isJ+qiAVCJJS1qCDcQ@mail.gmail.com> (raw)
In-Reply-To: <87k1wo1pfu.fsf@fifthhorseman.net>
On Thu, Jan 11, 2018 at 2:43 PM, Daniel Kahn Gillmor
<dkg@fifthhorseman.net> wrote:
> Matthias was suggesting a simply-named meta-package: just "wireguard",
> which would ensure that both wireguard-dkms and wireguard-tools are
> installed. The advantage there is that you can tell people to do:
>
> apt install wireguard
>
> and apt make sure the system has the common setup by default :)
This is a great idea. Let me know if you wind up making this. I've
added Egbert to the CC so that he can make an identical change in the
Ubuntu PPA.
Jason
next prev parent reply other threads:[~2018-01-11 14:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 13:49 Jason A. Donenfeld
2018-01-09 14:59 ` Matthias Urlichs
2018-01-09 15:20 ` Daniel Kahn Gillmor
2018-01-09 17:38 ` Jason A. Donenfeld
2018-01-10 7:09 ` Daniel Kahn Gillmor
2018-01-10 8:50 ` Matthias Urlichs
2018-01-10 22:30 ` Daniel Kahn Gillmor
2018-01-11 6:37 ` Stefan Tatschner
2018-01-11 13:43 ` Daniel Kahn Gillmor
2018-01-11 15:02 ` Jason A. Donenfeld [this message]
2018-01-11 23:38 ` Daniel Kahn Gillmor
2018-01-12 15:50 ` Egbert Verhage
2018-01-12 19:45 ` Jason A. Donenfeld
2018-01-12 7:40 ` Stefan Tatschner
2018-01-10 8:59 ` Jonathon Fernyhough
2018-01-11 15:00 ` Jason A. Donenfeld
2018-01-09 17:19 ` Germano Massullo
2018-01-13 16:30 ` Some gossip M. Dietrich
2018-01-13 21:25 ` Jason A. Donenfeld
2018-01-30 12:07 ` WireGuard in systemd-networkd Jörg Thalheim
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='CAHmME9q8_4Ln=OB7_NDTzE3JpTdf8Ae4isJ+qiAVCJJS1qCDcQ@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=dkg@fifthhorseman.net \
--cc=egbert@eggiecode.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).