Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Joe Doss <joe@solidadmin.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Seeking Fedora Maintainer
Date: Mon, 19 Dec 2016 01:21:20 +0100	[thread overview]
Message-ID: <CAHmME9qvC4DGkU0v3c87R9SDwyqViO4J6QBHmJux9yusU18=wg@mail.gmail.com> (raw)
In-Reply-To: <159146feaa0.2768.fd5e59abeac6319e4fe4e8192ea7d08d@solidadmin.com>

Hey Joe,

Nice to hear you're still out there, and huge congratulations on your
new kid! This is the best possible reply we could receive.

If you do automate the git build, be sure to build just based on newly
released tags, not on every commit. Also, since you last updated, the
tags have lost their `experimental-` prefix, which will slightly
change the URL. As well, for DKIM, there's now the `make dkim-install`
target, so that you don't have to manage which files are necessary
yourself. Check out what the Arch build does --
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=wireguard --
and if you look in the Makefile, you'll find quite a few paths that
you can override with environment variables, to match your liking.

Finally, please don't hesitate to get help in the maintenance burden
from potential others who might be around who could help.

Jason

  reply	other threads:[~2016-12-19  0:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19  0:13 Jason A. Donenfeld
2016-12-19  0:16 ` Joe Doss
2016-12-19  0:21   ` Jason A. Donenfeld [this message]
2016-12-23  3:57 ` Jason A. Donenfeld
2017-02-28 16:28   ` Jason A. Donenfeld
2017-03-03  3:58     ` Joe Doss

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='CAHmME9qvC4DGkU0v3c87R9SDwyqViO4J6QBHmJux9yusU18=wg@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=joe@solidadmin.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 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).