From: Jonathon Fernyhough <jonathon.fernyhough@york.ac.uk>
To: wireguard@lists.zx2c4.com
Subject: Re: WireGuard in systemd-networkd
Date: Wed, 10 Jan 2018 08:59:22 +0000 [thread overview]
Message-ID: <f575ed7d-47a8-d90c-384a-16351a4f84a5@york.ac.uk> (raw)
In-Reply-To: <87efmy42c0.fsf@fifthhorseman.net>
[-- Attachment #1.1: Type: text/plain, Size: 1208 bytes --]
On 10/01/18 07:09, Daniel Kahn Gillmor wrote:
> systemd-networkd is shipped (but by default disabled) in the systemd
> package itself.
>
> At the moment, wireguard-dkms (the kernel module package) Recommends:
> wireguard-tools (which supplies wg(8)), which i'd write as:
>
> 0) Recommends: wireguard-tools
>
> So i think we have several other choices:
>
> 1) Recommends: systemd | wireguard-tools
>
> 2) Recommends: wireguard-tools | systemd
>
> 3) Recommends: wireguard-tools, systemd
>
> 4) Recommends: wireguard-tools
> Suggests: systemd
>
>
> Of the above, i think i'll probably either stick with 0 or move to 4.
Sticking with 0) makes most sense to me. Just because systemd (>=
23something) supports wireguard, if wireguard-dkms can't rely on the
support being there then recommending its "own" tools is more reliable,
and more portable.
Alternatively, perhaps an "Enhances: systemd" ? e.g. wireguard-dkms
doesn't _need_ systemd, doesn't work any _better_ with systemd, but
definitely adds something _to_ systemd.
J
[1]
https://www.debian.org/doc/debian-policy/#binary-dependencies-depends-recommends-suggests-enhances-pre-depends
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2018-01-10 8:56 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 [this message]
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=f575ed7d-47a8-d90c-384a-16351a4f84a5@york.ac.uk \
--to=jonathon.fernyhough@york.ac.uk \
--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).