From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Jasper Knockaert <jasper@knockaert.nl>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>,
unit193@ubuntu.com, Andy Whitcroft <apw@canonical.com>
Subject: Re: Migrating From Ubuntu PPA to Real Ubuntu Packages
Date: Mon, 3 Aug 2020 13:42:31 +0200 [thread overview]
Message-ID: <CAHmME9osZQrxe4VMXXVPxz-O50nxiSq5xkPNDMEBYgJZ07rGUg@mail.gmail.com> (raw)
In-Reply-To: <4FD17BFB-009E-4367-A208-5614EC3FAC02@knockaert.nl>
On Mon, Aug 3, 2020 at 12:36 PM Jasper Knockaert <jasper@knockaert.nl> wrote:
> Well, I think there is a case to manually install wireguard-tools where
> you want to run wireguard in a container. In that case you may want to
> install wireguard-dkms on the host (in case its kernel doesn't yet
> support wireguard), and wireguard-tools in the container.
That's a good point. There are all sorts of unusual cases where one
_might_ want to select individual packages instead of the meta
package. But if you don't know what you're doing, `sudo apt install
wireguard` is the mnemonic most people probably want. And for the
purposes of transitioning away from the PPA, that probably has the
least friction. But you're right: containerization is one instance in
which the meta package might not be desired.
next prev parent reply other threads:[~2020-08-03 11:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 10:28 Jason A. Donenfeld
2020-08-03 10:36 ` Jasper Knockaert
2020-08-03 11:42 ` Jason A. Donenfeld [this message]
2020-08-03 16:08 ` NoddingDog
2020-08-03 16:21 ` Jason A. Donenfeld
2020-08-03 16:25 ` NoddingDog
2020-08-03 16:28 ` Jason A. Donenfeld
2020-08-03 16:30 ` Jason A. Donenfeld
2020-08-03 16:43 ` NoddingDog
2020-08-03 16:47 ` Jason A. Donenfeld
2020-08-03 16:49 ` NoddingDog
[not found] ` <532c74129f32cffd53c71b87858929f800c2f87b.camel@noddingdog.org>
2020-08-03 16:42 ` Jason A. Donenfeld
2020-08-04 12:36 ` Andy Whitcroft
2020-08-04 13:26 ` Jason A. Donenfeld
2020-08-04 12:49 ` Andy Whitcroft
2020-08-04 13:14 ` Jason A. Donenfeld
2020-08-03 21:18 ` Andy Whitcroft
2020-08-03 21:24 ` Jason A. Donenfeld
2020-08-04 21:58 ` Jason A. Donenfeld
2020-08-05 6:23 ` NoddingDog
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=CAHmME9osZQrxe4VMXXVPxz-O50nxiSq5xkPNDMEBYgJZ07rGUg@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=apw@canonical.com \
--cc=jasper@knockaert.nl \
--cc=unit193@ubuntu.com \
--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).