From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?G=C3=A1bor_Boskovits?= Subject: Re: Custom wireguard shepherd service Date: Thu, 12 Mar 2020 08:09:53 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:35759) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jCHyt-0004zB-1B for help-guix@gnu.org; Thu, 12 Mar 2020 03:10:12 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jCHyp-0000Ew-8F for help-guix@gnu.org; Thu, 12 Mar 2020 03:10:10 -0400 Received: from mail-wr1-x434.google.com ([2a00:1450:4864:20::434]:40407) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1jCHyp-0000EN-1k for help-guix@gnu.org; Thu, 12 Mar 2020 03:10:07 -0400 Received: by mail-wr1-x434.google.com with SMTP id p2so5973731wrw.7 for ; Thu, 12 Mar 2020 00:10:06 -0700 (PDT) In-Reply-To: List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane-mx.org@gnu.org Sender: "Help-Guix" To: Gregory Katz Cc: help-guix Hello Gregory, Gregory Katz via ezt =C3=ADrta (id=C5=91pont: 2020. m= =C3=A1rc. 12., Cs=C3=BC 4:48): > Hi all, > > I'm trying to put together a wireguard shepherd service that operates > similar to the current nftables service, i.e., the service works by runni= ng > a utility program (in this case a shell script called wg-quick) with a > configuration file. Unfortunately, wg-quick, which is included in the > wireguard-tools package, does not work with files interred by guix (the > file names are too long). To make it work, I have to patch wg-quick. > > Can anyone point me to where I can read up on how to apply a patch during > the wireguard-tools build process? > You can run a search against the keyword search-patches in a package module to see how patches are included in a package definition. If the patch only does simple regexp substitution, you can also consider using a phase with substitute*. There are a lot of packages using that. If you need to have a patch, then you should add it to the gnu/packages/patches directory, and also to the local.mk file patches variable, so that the build picks it up. You can search the git log for adding or removing a patch, so that you see how it is done. > > Thanks very much for the help, > > Greg > > Sent with [ProtonMail](https://protonmail.com) Secure Email. Best regards, g_bor