From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Andrej Kacian <andrej@kacian.sk>
Cc: wireguard@lists.zx2c4.com
Subject: Re: making wireguard work on RHEL7/etc.
Date: Tue, 27 Jun 2017 13:08:14 +0200 [thread overview]
Message-ID: <20170627110812.GD3026@zx2c4.com> (raw)
In-Reply-To: <20170627113906.391bb9a6.andrej@kacian.sk>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
On Tue, Jun 27, 2017 at 11:39:06AM +0200, Andrej Kacian wrote:
> On Tue, 27 Jun 2017 08:25:31 +0100 (BST)
> wireguard@wut.to wrote:
>
> > > I wonder - is it a good idea to depend on
> > > nonstandard, distribution-specific defines like this? This kind of
> > > modification IMHO belongs in a local patch applied during a rpmbuild
> > > for a RHEL/Centos package.
> >
> > I think that depends entirely on if you want it to be easy for users
> > to obtain and use your software. If it requires constant patching and
> > updates, most people won't bother and will use something else.
>
> Absolutely. I'm not saying these fixes are not needed, I merely
> expressed an opinion that their place is not in the main source code,
> but rather in a custom patch applied when creating packages for the
> affected distribution(s).
compat.h is a dumpster fire already. Tons of people use the RHEL kernel.
I think supporting it won't make an already gross cess pool any more
disgusting. It's a file of hacks; I might as well add another.
(I probably won't add hacks, though, for the heaps of random custom
Android vendor kernels.)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-06-27 10:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 15:18 wireguard
2017-06-26 8:07 ` Aaron Muir Hamilton
2017-06-26 8:19 ` wireguard
2017-06-26 9:04 ` Jason A. Donenfeld
2017-06-26 9:25 ` wireguard
2017-06-26 9:57 ` Jason A. Donenfeld
2017-06-26 10:47 ` Jason A. Donenfeld
2017-06-26 19:55 ` wireguard
2017-06-27 11:02 ` Jason A. Donenfeld
2017-06-26 20:45 ` wireguard
2017-06-27 11:05 ` Jason A. Donenfeld
2017-06-27 11:38 ` wireguard
2017-06-27 19:23 ` Jason A. Donenfeld
2017-06-27 19:43 ` wireguard
2017-06-27 19:59 ` Jason A. Donenfeld
2017-06-27 20:22 ` Jason A. Donenfeld
2017-06-27 20:52 ` Jason A. Donenfeld
2017-06-27 21:30 ` wireguard
2017-06-27 22:09 ` Jason A. Donenfeld
2017-06-27 5:35 ` Andrej Kacian
2017-06-27 7:25 ` wireguard
2017-06-27 9:39 ` Andrej Kacian
2017-06-27 11:08 ` Jason A. Donenfeld [this message]
2018-04-05 15:08 ` Daniel Kahn Gillmor
2018-04-05 16:15 ` Daniel Kahn Gillmor
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=20170627110812.GD3026@zx2c4.com \
--to=jason@zx2c4.com \
--cc=andrej@kacian.sk \
--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).