Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Dario Pilori <dario.pilori@astrogeo.va.it>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: WireGuard fails to build on CentOS 7.1908
Date: Fri, 6 Sep 2019 16:47:29 -0600	[thread overview]
Message-ID: <CAHmME9odNo2d+=u1z7kNuXKy2HYzOqaHt_0N9Dz49kZFp4qW_g@mail.gmail.com> (raw)
In-Reply-To: <816bb8ff-101f-2719-4b75-1d194c519aef@astrogeo.va.it>

Hey Dario,

I'm not super familiar with the RHEL release varieties. Maybe you or
somebody can clarify and help define how we'll approach it?

What we've done in the past is support whatever the "latest" RHEL
kernel is. IIRC, 7.6 was released not so long ago, and we did the
compat.h work on 7.6, and then dropped support for RHEL 7.5. It sounds
to me like what you're saying now is that 7.6 has already been
replaced by 7.7? Or there's a stable 7.6 and then an "in-development"
7.7 that is rolling? If it's the latter case, do you know if that's
widely used and worthwhile for us to support?

In other words, I'm not so sure of the RHEL landscape, but if you make
a description and argument for what we should support in WireGuard's
compat layer, as long as it's somewhat reasonable, I'm happy to
oblige.

Jason
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2019-09-06 22:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-31 16:00 Dario Pilori
2019-09-06 19:17 ` Jason A. Donenfeld
2019-09-06 21:23   ` Dario Pilori
2019-09-06 22:47     ` Jason A. Donenfeld [this message]
2019-09-07  7:41       ` Dario Pilori
2019-09-14  4:44         ` 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='CAHmME9odNo2d+=u1z7kNuXKy2HYzOqaHt_0N9Dz49kZFp4qW_g@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=dario.pilori@astrogeo.va.it \
    --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).