From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard in systemd-networkd
Date: Thu, 11 Jan 2018 16:00:55 +0100 [thread overview]
Message-ID: <CAHmME9o4oMAuW5n0f06-XAF+=kovi7BEi4GE3xjQ1-awrxgNvA@mail.gmail.com> (raw)
In-Reply-To: <87efmy42c0.fsf@fifthhorseman.net>
Hey Daniel,
On Wed, Jan 10, 2018 at 8:09 AM, Daniel Kahn Gillmor
<dkg@fifthhorseman.net> wrote:
> cool. this sounds very much like you've decided that the netlink
> interface is now stable, which is good to hear
Yep!
> 0) Recommends: wireguard-tools
> 4) Recommends: wireguard-tools
> Suggests: systemd
>
>
> Of the above, i think i'll probably either stick with 0 or move to 4.
> given what you said above, i don't really like the idea of using the
> disjunction; people already running systemd will have systemd-networkd
> available; and i don't want the wireguard-dkms package to encourage
> people to install systemd if they've already made a decision to avoid
> the default and not use it.
I think it probably makes most sense to stick with 0.
Jason
next prev parent reply other threads:[~2018-01-11 14:58 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
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 [this message]
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='CAHmME9o4oMAuW5n0f06-XAF+=kovi7BEi4GE3xjQ1-awrxgNvA@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=dkg@fifthhorseman.net \
--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).