All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <WireGuard@lists.zx2c4.com>
Subject: Re: [WireGuard] Comments on wgserver.service
Date: Wed, 6 Jul 2016 10:47:15 -0500	[thread overview]
Message-ID: <20160706154715.GA8543@wolff.to> (raw)
In-Reply-To: <CAHmME9qMVsQ1GDMRu862dNJqw006HuGCv4mPdBb7h8urmQOp+g@mail.gmail.com>

On Wed, Jul 06, 2016 at 17:22:57 +0200,
  "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>On Wed, Jul 6, 2016 at 5:19 PM, Bruno Wolff III <bruno@wolff.to> wrote:
>> Potentially I could get involved with packing wg on Fedora, but there isn't
>> much point until the kernel part is upstream.
>
>Actually Fedora has quite a few modules in packages that aren't
>upstream. They use dkms or akmod.

I thought those usually end up in rpmfusion, copr or other external repos, 
rather than Fedora proper.

I'd still like to see if it is going to land upstream. Even if it ends up 
in 4.9, it'd probably be simpler to just wait and package the wg part 
when the kernel part is included with the Fedora kernel. If upstream declines 
merging it, then things would be different as we'd need to use dkms or akmod 
to make the packages easy to use.

  reply	other threads:[~2016-07-06 15:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-06 12:04 [WireGuard] Comments on wgserver.service Bruno Wolff III
2016-07-06 14:33 ` Jason A. Donenfeld
2016-07-06 15:19   ` Bruno Wolff III
2016-07-06 15:22     ` Jason A. Donenfeld
2016-07-06 15:47       ` Bruno Wolff III [this message]
2016-07-06 15:58         ` Jason A. Donenfeld
2016-07-06 15:28   ` 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=20160706154715.GA8543@wolff.to \
    --to=bruno@wolff.to \
    --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.