Github messages for voidlinux
 help / color / mirror / Atom feed
From: gspe <gspe@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: nextdns-1.4.35
Date: Fri, 29 May 2020 09:58:47 +0200	[thread overview]
Message-ID: <20200529075847.2otB0E14Y1DvxodxCr5w0bTE6WBWxptC8BnBYf3fJAU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20022@inbox.vuxu.org>

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

There is an updated pull request by gspe against master on the void-packages repository

https://github.com/gspe/void-packages nextdns
https://github.com/void-linux/void-packages/pull/20022

New package: nextdns-1.4.35
Close #19905 


A patch file from https://github.com/void-linux/void-packages/pull/20022.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-nextdns-20022.patch --]
[-- Type: text/x-diff, Size: 1903 bytes --]

From 6dc2b4871520a4dec113e0e8cbfc07371d6c58f4 Mon Sep 17 00:00:00 2001
From: Giuseppe Fierro <gspe@ae-design.ws>
Date: Tue, 10 Mar 2020 17:32:03 +0100
Subject: [PATCH] New package: nextdns-1.6.3

---
 srcpkgs/nextdns/files/nextdns.conf |  5 +++++
 srcpkgs/nextdns/files/nextdnsd/run |  2 ++
 srcpkgs/nextdns/template           | 19 +++++++++++++++++++
 3 files changed, 26 insertions(+)
 create mode 100644 srcpkgs/nextdns/files/nextdns.conf
 create mode 100644 srcpkgs/nextdns/files/nextdnsd/run
 create mode 100644 srcpkgs/nextdns/template

diff --git a/srcpkgs/nextdns/files/nextdns.conf b/srcpkgs/nextdns/files/nextdns.conf
new file mode 100644
index 00000000000..c31676ef24f
--- /dev/null
+++ b/srcpkgs/nextdns/files/nextdns.conf
@@ -0,0 +1,5 @@
+# Configuration for NextDNS
+
+# NextDNS custom configuration id
+# change id with your NextDNS id
+config id
diff --git a/srcpkgs/nextdns/files/nextdnsd/run b/srcpkgs/nextdns/files/nextdnsd/run
new file mode 100644
index 00000000000..e23469eb39d
--- /dev/null
+++ b/srcpkgs/nextdns/files/nextdnsd/run
@@ -0,0 +1,2 @@
+#!/bin/sh
+exec nextdns run -config-file /etc/nextdns/nextdns.conf 2>&1
diff --git a/srcpkgs/nextdns/template b/srcpkgs/nextdns/template
new file mode 100644
index 00000000000..1288313752b
--- /dev/null
+++ b/srcpkgs/nextdns/template
@@ -0,0 +1,19 @@
+# Template file for 'nextdns'
+pkgname=nextdns
+version=1.6.3
+revision=1
+build_style=go
+go_import_path=github.com/nextdns/nextdns
+short_desc="NextDNS CLI client (DoH Proxy)"
+maintainer="Giuseppe Fierro <gspe@ae-design.ws>"
+license="MIT"
+homepage="https://nextdns.io/"
+distfiles="https://github.com/${pkgname}/${pkgname}/archive/v${version}.tar.gz"
+checksum=ffc9b60be659f2b16c0c65477571689d345b8afe423c3394ed740e8e544169ed
+conf_files="/etc/nextdns/nextdns.conf"
+
+post_install() {
+	vsv nextdnsd
+	vinstall ${FILESDIR}/nextdns.conf 640 etc/nextdns
+	vlicense LICENSE
+}

  parent reply	other threads:[~2020-05-29  7:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20022@inbox.vuxu.org>
2020-05-28 19:42 ` Vaelatern
2020-05-29  7:58 ` gspe [this message]
2020-05-29 12:39 ` New package: nextdns-1.6.3 imbsky
2022-04-16  2:02 ` New package: nextdns-1.6.4 github-actions
2022-04-30  2:13 ` [PR PATCH] [Closed]: " github-actions

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=20200529075847.2otB0E14Y1DvxodxCr5w0bTE6WBWxptC8BnBYf3fJAU@z \
    --to=gspe@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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).