From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Christian Hesse <list@eworm.de>
Cc: Christian Hesse <mail@eworm.de>,
WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH v2 1/1] add dkms configuration file dkms.conf
Date: Tue, 6 Dec 2016 19:14:47 +0100 [thread overview]
Message-ID: <CAHmME9rxy-tzWdOYontRYDkxwWAgyx6jPURej1Qh2brMcrDEjw@mail.gmail.com> (raw)
In-Reply-To: <20161206103551.038a3d3e@leda>
On Tue, Dec 6, 2016 at 10:35 AM, Christian Hesse <list@eworm.de> wrote:
> "Jason A. Donenfeld" <Jason@zx2c4.com> on Sat, 2016/12/03 23:21:
> > I like the general idea here of including dkim in WireGuard now,
>
> 'dkim' is mail security... We have dkms. ;)
Lol!
> For Arch Linux we install dkms sources to /usr/src/$pkgname-$pkgver, so for
> wireguard we have: /usr/src/wireguard-0.0.20161129/
> To have something like this would be great:
> make DESTDIR="$pkgdir/" DKMSDIR="/usr/src/$pkgname-$pkgver" dkms
How does this look to you:
https://git.zx2c4.com/WireGuard/commit/?id=b70677fb8af28cbaec810146144858ad07a879ed
You can simply run:
make DESTDIR="$pkgdir/" DKMSDIR="/usr/src/$pkgname-$pkgver" dkms-install
You can also adjust SRCDIR or PREFIX, but I imagine you'll want to
keep these as is. All variables are also inherited from the
environment, so if the package manager sets these globally, things are
even easier.
What do you think of that?
next prev parent reply other threads:[~2016-12-06 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-03 12:30 [PATCH " Christian Hesse
2016-12-03 12:42 ` [PATCH v2 " Christian Hesse
2016-12-03 22:21 ` Jason A. Donenfeld
2016-12-06 9:35 ` Christian Hesse
2016-12-06 18:14 ` Jason A. Donenfeld [this message]
2016-12-06 18:57 ` Jason A. Donenfeld
2016-12-06 20:15 ` Christian Hesse
2016-12-06 21:31 ` 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=CAHmME9rxy-tzWdOYontRYDkxwWAgyx6jPURej1Qh2brMcrDEjw@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=list@eworm.de \
--cc=mail@eworm.de \
--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).