From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Matthias Urlichs <matthias@urlichs.de>, wireguard@lists.zx2c4.com
Subject: Re: WireGuard in systemd-networkd
Date: Wed, 10 Jan 2018 17:30:00 -0500 [thread overview]
Message-ID: <87wp0p1h5j.fsf@fifthhorseman.net> (raw)
In-Reply-To: <81bb0726-8f67-0163-875f-0d3403f8df29@urlichs.de>
[-- Attachment #1: Type: text/plain, Size: 707 bytes --]
On Wed 2018-01-10 09:50:39 +0100, Matthias Urlichs wrote:
> I would also create a virtual "wireguard" package that directly depends
> on wireguard-dkms and wireguard-tools (and Recommends:
> networkmanager-wireguard, as soon as that exists). Then, simply instruct
> the user to install that.
This is a good idea, thanks! As an aside, if anyone wants to suggest
packaging improvements like this, a bug report to the debian BTS is
probably the easiest way to go.
As for the dependencies related to systemd-networkd, the discussion here
makes me think we're better off just sticking with the status quo
(option 0), so i'll do that unless i hear a really compelling argument
to do anything else.
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-01-11 2: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 [this message]
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
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=87wp0p1h5j.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=matthias@urlichs.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;
as well as URLs for NNTP newsgroup(s).