organization of wireguard linux kernel repos moving forward

Jason A. Donenfeld Jason at zx2c4.com
Thu Dec 26 18:45:05 CET 2019


On Mon, Dec 9, 2019 at 12:56 PM Jason A. Donenfeld <Jason at zx2c4.com> wrote:
> With WireGuard in net-next, it's time to break up the monolithic repo
> we've been using for development into something a bit more manageable
> and in line with ordinary kernel development.
>
> Right now the "WireGuard.git" repo has been structured as an out of
> tree module, alongside a subdirectory for tools, one for scripts, one
> for tests, and another for a super gnarly compat layer that makes the
> thing work on all kernels going back to 3.10. We're going to break
> this up into three repositories:
>
> 1) wireguard-linux.git will be a full Linux tree, with wireguard
> changes, and regularly merge in net/net-next, and have things from
> there posted on netdev like usual for review. This repo won't be an
> out of tree module any more, obviously.
> https://git.zx2c4.com/wireguard-linux/
>
> 2) wireguard-tools.git will have the userspace utilities and scripts,
> such as wg(8) and wg-quick(8), and be easily packageable by distros.
> https://git.zx2c4.com/wireguard-tools/
>
> 3) wireguard-linux-compat.git will be an out-of-tree module containing
> the aforementioned horrific compat.h layer. New development will go
> into upstream wireguard-linux.git, but we'll do our best to keep
> things mostly working for as long as it makes sense and is feasible.
> https://git.zx2c4.com/wireguard-linux-compat/
>
> The CI that runs on build.wireguard.com will also see some updates to
> reflect these adjustments, and also more closely align with the
> net-next tree. Additionally, I'm interested to see if I can make our
> CI useful for a variety of things in net/ and drivers/net/ instead of
> just for wireguard.

The above changes are now complete.


More information about the WireGuard mailing list