WireGuard Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Hesse <list@eworm.de>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
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 21:15:47 +0100	[thread overview]
Message-ID: <20161206211547.1e3dd9a5@leda> (raw)
In-Reply-To: <CAHmME9rxy-tzWdOYontRYDkxwWAgyx6jPURej1Qh2brMcrDEjw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1529 bytes --]

"Jason A. Donenfeld" <Jason@zx2c4.com> on Tue, 2016/12/06 19:14:
> 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?

Looks good!

Here are my changes for the git package:

https://aur.archlinux.org/cgit/aur.git/commit/?h=wireguard-git&id=dbb8a8cd7a98d3e5d338a4c1103eb7fae1b4c40c

Thanks a lot!
-- 
main(a){char*c=/*    Schoene Gruesse                         */"B?IJj;MEH"
"CX:;",b;for(a/*    Best regards             my address:    */=0;b=c[a++];)
putchar(b-1/(/*    Chris            cc -ox -xc - && ./x    */b/42*2-3)*42);}

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2016-12-06 20:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-03 12:30 [PATCH 1/1] add dkms configuration file dkms.conf 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
2016-12-06 18:57         ` Jason A. Donenfeld
2016-12-06 20:15         ` Christian Hesse [this message]
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=20161206211547.1e3dd9a5@leda \
    --to=list@eworm.de \
    --cc=Jason@zx2c4.com \
    --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