From: Bruno Wolff III <bruno@wolff.to>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: zorun@bitsofnetworks.org, Christian Hesse <mail@eworm.de>,
zx2c4@gentoo.org, wireguard@lists.zx2c4.com
Subject: Re: [WireGuard] The Distro Package Maintainers Thread
Date: Thu, 30 Jun 2016 09:45:58 -0500 [thread overview]
Message-ID: <20160630144558.GA5133@wolff.to> (raw)
In-Reply-To: <CAHmME9oiTG6Hfps0ZqJFJ13UxappXk3TyoLWWu0AZ_G_A65bxQ@mail.gmail.com>
On Thu, Jun 30, 2016 at 14:52:04 +0200,
"Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
>Christophe: Fedora (which will then travel downstream to RHEL?) He
>doesn't have time for this now, but including him in the thread
>anyway, and hopefully he'll kindly forward this email onto someone
>else he knows at Redhat
Fedora people can publish EPEL packages, but I'm don't know Red Hat's
stance on kernel module packages.
For Fedora, not having it in the upstream kernel will make it very difficult
to get in Fedora proper, and doing COPRs may be a pain since kernel builds
happen a lot for Fedora.
When it is actually in Fedora there won't be a package for the kernel module
(as it will be part of the kernel-modules or kernel-modules-extra packages).
If it does get accepted for say 4.8, then getting a backported version into
previously released Fedora's that may be running older kernels may be
possible.
>=== 3. Versioning ===
>
> 0.0.20160701
Fedora splits the version into two pieces. The first part is the version
and would be something like 0.0. As a prerelease the release should be
0.x.dateandorcommit, where x is an integer that gets bumped every release
and the rest can be a mix of date, tag or commit ID.
So the final version might look like 0.0-0.1.20160701 .
next prev parent reply other threads:[~2016-06-30 14:44 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 12:52 [WireGuard] The Distro Package Maintainers Thread Jason A. Donenfeld
2016-06-30 13:28 ` Christian Hesse
2016-06-30 14:45 ` Bruno Wolff III [this message]
2016-06-30 15:03 ` Daniel Kahn Gillmor
2016-07-01 16:40 ` [WireGuard] debian packaging [was: Re: The Distro Package Maintainers Thread] Daniel Kahn Gillmor
2016-07-01 21:05 ` Jason A. Donenfeld
2016-07-01 21:11 ` Jason A. Donenfeld
2016-07-02 12:38 ` Daniel Kahn Gillmor
2016-07-06 22:34 ` Jason A. Donenfeld
2016-07-08 21:20 ` Daniel Kahn Gillmor
2016-06-30 15:30 ` [WireGuard] The Distro Package Maintainers Thread Baptiste Jonglez
2016-06-30 18:32 ` Jason A. Donenfeld
2016-06-30 18:42 ` Jason A. Donenfeld
2016-06-30 19:27 ` Christian Hesse
2016-06-30 19:34 ` Jason A. Donenfeld
2016-07-01 2:41 ` Jason A. Donenfeld
2016-07-01 12:26 ` Daniel Kahn Gillmor
2016-07-01 21:28 ` Jason A. Donenfeld
2016-07-01 21:45 ` Christian Hesse
2016-07-02 12:39 ` Daniel Kahn Gillmor
2016-07-02 15:55 ` Daniel Kahn Gillmor
2016-07-04 15:50 ` Jason A. Donenfeld
2016-07-04 22:57 ` Phillip Smith
2016-07-04 23:46 ` Jason A. Donenfeld
2016-07-05 1:15 ` Phillip Smith
2016-07-05 1:23 ` Jason A. Donenfeld
2016-07-05 19:05 ` Christian Hesse
2016-07-11 17:51 ` Jason A. Donenfeld
2016-07-11 21:20 ` Baptiste Jonglez
2016-07-11 22:34 ` Jason A. Donenfeld
2016-07-12 10:59 ` Daniel Kahn Gillmor
2016-07-12 15:27 ` Jason A. Donenfeld
2016-07-13 14:29 ` Jason A. Donenfeld
2016-07-13 16:35 ` Jason A. Donenfeld
[not found] ` <CAHmME9qQ=46ZyPLPAw8sDb1bhwWGdEcxoFpof3meV+WUKHrMfg@mail.gmail.com>
2016-07-13 16:42 ` Jason A. Donenfeld
2016-07-13 16:49 ` Baptiste Jonglez
2016-07-13 17:58 ` Jason A. Donenfeld
2016-07-13 18:15 ` Martin Hauke
2016-07-13 21:57 ` Daniel Kahn Gillmor
2016-07-14 14:27 ` Jason A. Donenfeld
2016-07-14 14:30 ` 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=20160630144558.GA5133@wolff.to \
--to=bruno@wolff.to \
--cc=Jason@zx2c4.com \
--cc=mail@eworm.de \
--cc=wireguard@lists.zx2c4.com \
--cc=zorun@bitsofnetworks.org \
--cc=zx2c4@gentoo.org \
/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.