From: Christian Hesse <list@eworm.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: FAQ and quickstart
Date: Mon, 16 Jan 2017 14:33:56 +0100 [thread overview]
Message-ID: <20170116143356.561bf7cb@leda> (raw)
In-Reply-To: <CAHmME9rS7+kRyWtOwZMtxzmfrk_vqx2+iGFsNTuO8usrpBfOHA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
"Jason A. Donenfeld" <Jason@zx2c4.com> on Mon, 2017/01/16 14:26:
> Hi Christian,
>
> Should the wireguard Arch package depend on linux-headers? Or the dkms
> package on linux-headers? Or is it just the Arch-way that dkms merely
> prints a warning but doesn't actually have real package deps?
We have several linux packages in our repositories. Users may use linux-lts,
linux-zen, linux-grsec or anything from AUR with the corresponding headers
package. Depending on 'linux-headers' would force the users to install linux
and linux-headers packages.
Even the tools' dependency on the module is something people complain about...
So I think I will keep things as-is. Users are advised to read install
messages. :-P
--
main(a){char*c=/* Schoene Gruesse */"B?IJj;MEH"
"CX:;",b;for(a/* Best regards my address: */=0;b=c[a++];)
putchar(b-1/(/* Chris cc -ox -xc - && ./x */b/42*2-3)*42);}
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-01-16 13:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 11:31 FAQ and quickstart lennart
2017-01-16 11:32 ` Jason A. Donenfeld
2017-01-16 13:13 ` Jörg Thalheim
2017-01-16 13:23 ` lennart
2017-01-16 13:26 ` Jason A. Donenfeld
2017-01-16 13:33 ` Christian Hesse [this message]
2017-01-16 13:34 ` Jason A. Donenfeld
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=20170116143356.561bf7cb@leda \
--to=list@eworm.de \
--cc=Jason@zx2c4.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.