wireguard.lists.zx2c4.com archive mirror
 help / color / mirror / Atom feed
From: John <graysky@archlinux.us>
To: Davide Depau <davide@depau.eu>
Cc: Christian Hesse <mail@eworm.de>,
	WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: binary module for arch?
Date: Mon, 31 Dec 2018 11:11:30 -0500	[thread overview]
Message-ID: <CAO_nJAYw_zbNBsxtaKbR=kxp-+E4d2VkzUfrWtnSn26ZVkuEMw@mail.gmail.com> (raw)
In-Reply-To: <CAMp63jVKAeieefottP=EwYMeo0daD5GDxwpT1PiPPOZQkQ6gSA@mail.gmail.com>

Our package manager, pacman, will display optional dependencies to
users/most known to inspect the output.

My recommendation is to change the wording under the command on your
install page to something like: "Users of the distro provided kernels
(linux and linux-lts) may download the requisite corresponding
precompiled wireguard module. Users of custom kernels will require the
wireguard-dkms package and corresponding kernel headers to compile the
module."

For your info, example pacman output that most Arch users will be
accustom to reading upon installation of the wireguard-tools package:

% sudo pacman -S wireguard-tools
resolving dependencies...
looking for conflicting packages...

Packages (1) wireguard-tools-0.0.20181218-2

Total Installed Size:  0.21 MiB

:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring
[#############################] 100%
(1/1) checking package integrity
[#############################] 100%
(1/1) loading package files
[#############################] 100%
(1/1) checking for file conflicts
[#############################] 100%
:: Processing package changes...
(1/1) installing wireguard-tools
[#############################] 100%
Optional dependencies for wireguard-tools
    openresolv: for DNS functionality [installed]
    wireguard-dkms: wireguard module, built by dkms
    wireguard-arch: wireguard module for linux
    wireguard-lts: wireguard module for linux-lts
:: Running post-transaction hooks...
(1/2) Reloading system manager configuration...
(2/2) Arming ConditionNeedsUpdate...


On Sun, Dec 30, 2018 at 8:50 PM Davide Depau <davide@depau.eu> wrote:
>
> Hi Jason,
> sorry for sneaking into the conversation but I'm currently using wireguard-dkms. I think deprecating it would be a bad idea: anyone who uses a custom kernel cannot use the binary modules.
> I'm currently using linux-hardened on my server (yeah, I run Arch Linux on my personal server lol) and rely on the dkms package for the wireguard module.
> Binary packages should probably be preferred for those who use the default kernels, however not everyone does.
> That being said I really hope WireGuard makes it to mainline soon ;)
>
> Regards,
> Davide
>
> On Mon, Dec 31, 2018, 1:59 AM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>>
>> Hey Christian,
>>
>> I noticed there are now two distro-built packages for wireguard for
>> arch -- wireguard-lts and wireguard-arch. These seem probably more
>> convenient for most people than the dkms one. What would you recommend
>> in terms of updating wireguard.com/install/ ? And do you plan on
>> depreciating the dkms one at some point, or do you think it will
>> remain useful for certain users?
>>
>> Regards,
>> Jason
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2018-12-31 17:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-31  0:58 binary module for arch? Jason A. Donenfeld
2018-12-31  1:48 ` Davide Depau
2018-12-31 16:11   ` John [this message]
2019-01-01 12:44     ` Jordan Glover
2019-01-01 20:54       ` Christian Hesse
2019-01-01 20:50 ` Christian Hesse
2019-01-02  0:22   ` Jason A. Donenfeld
2019-01-02  7:57     ` Christian Hesse

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='CAO_nJAYw_zbNBsxtaKbR=kxp-+E4d2VkzUfrWtnSn26ZVkuEMw@mail.gmail.com' \
    --to=graysky@archlinux.us \
    --cc=davide@depau.eu \
    --cc=mail@eworm.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).