Github messages for voidlinux
 help / color / mirror / Atom feed
From: MeganerdNL <MeganerdNL@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] New package: encrypted-dns
Date: Fri, 04 Aug 2023 11:37:13 +0200	[thread overview]
Message-ID: <20230804093713.L9r6Sa4fra20yfio_Dnvp6GSyujo-gm3Dgn_9dBb7yI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45381@inbox.vuxu.org>

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

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

https://github.com/MeganerdNL/void-packages encrypted-dns
https://github.com/void-linux/void-packages/pull/45381

New package: encrypted-dns
**DNSCrypt v2 server with support for DNSSEC, DoH forwarding and anonymized DNSCrypt**

#### Testing the changes
- I tested the changes in this PR: **YES**

#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**

#### Local build testing
- I built this PR locally for my native architecture, (x86_64-glibc)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - x86_64-musl
  - i686-glibc
  - aarch64-glibc
  - aarch64-musl
  - armv7l-glibc
  - armv7l-musl
  - armv6l-glibc
  - armv6l-musl

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

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

From 24f1e900149e8a435afb9a98cb937ce489026e83 Mon Sep 17 00:00:00 2001
From: MeganerdNL <meganerd@meganerd.nl>
Date: Sun, 30 Jul 2023 13:40:26 +0200
Subject: [PATCH] New package: encrypted-dns

---
 srcpkgs/encrypted-dns/INSTALL                 |  9 +++++
 srcpkgs/encrypted-dns/INSTALL.msg             |  7 ++++
 srcpkgs/encrypted-dns/files/encrypted-dns/run |  3 ++
 .../encrypted-dns/patches/cargo-lock.patch    | 11 +++++++
 srcpkgs/encrypted-dns/template                | 33 +++++++++++++++++++
 5 files changed, 63 insertions(+)
 create mode 100644 srcpkgs/encrypted-dns/INSTALL
 create mode 100644 srcpkgs/encrypted-dns/INSTALL.msg
 create mode 100755 srcpkgs/encrypted-dns/files/encrypted-dns/run
 create mode 100644 srcpkgs/encrypted-dns/patches/cargo-lock.patch
 create mode 100644 srcpkgs/encrypted-dns/template

diff --git a/srcpkgs/encrypted-dns/INSTALL b/srcpkgs/encrypted-dns/INSTALL
new file mode 100644
index 0000000000000..1fdde5c37b4ae
--- /dev/null
+++ b/srcpkgs/encrypted-dns/INSTALL
@@ -0,0 +1,9 @@
+case "$ACTION" in
+    post)
+        if [ "$UPDATE" = "yes" ] ; then
+            :
+        else
+            chmod 750 var/lib/encrypted-dns
+        fi
+        ;;
+esac
diff --git a/srcpkgs/encrypted-dns/INSTALL.msg b/srcpkgs/encrypted-dns/INSTALL.msg
new file mode 100644
index 0000000000000..6c6fcec3bc6d6
--- /dev/null
+++ b/srcpkgs/encrypted-dns/INSTALL.msg
@@ -0,0 +1,7 @@
+NOTE:
+Before enabling / starting the service, you must install a 
+configuration file in /etc/encrypted-dns/encrypted-dns.toml
+Example: /usr/share/examples/encrypted-dns/example-encrypted-dns.toml
+
+user/group for this package is: _encrypted_dns/_encrypted_dns
+The state file should be installed in /var/lib/encrypted-dns
diff --git a/srcpkgs/encrypted-dns/files/encrypted-dns/run b/srcpkgs/encrypted-dns/files/encrypted-dns/run
new file mode 100755
index 0000000000000..9bdff1794f551
--- /dev/null
+++ b/srcpkgs/encrypted-dns/files/encrypted-dns/run
@@ -0,0 +1,3 @@
+#!/bin/sh
+exec 2>&1
+exec encrypted-dns -c /etc/encrypted-dns/encrypted-dns.toml
diff --git a/srcpkgs/encrypted-dns/patches/cargo-lock.patch b/srcpkgs/encrypted-dns/patches/cargo-lock.patch
new file mode 100644
index 0000000000000..43092c2697e84
--- /dev/null
+++ b/srcpkgs/encrypted-dns/patches/cargo-lock.patch
@@ -0,0 +1,11 @@
+--- a/Cargo.lock
++++ b/Cargo.lock
+@@ -226,7 +226,7 @@
+ 
+ [[package]]
+ name = "encrypted-dns"
+-version = "0.9.12"
++version = "0.9.13"
+ dependencies = [
+  "anyhow",
+  "byteorder",
diff --git a/srcpkgs/encrypted-dns/template b/srcpkgs/encrypted-dns/template
new file mode 100644
index 0000000000000..044a5fabf0fec
--- /dev/null
+++ b/srcpkgs/encrypted-dns/template
@@ -0,0 +1,33 @@
+# Template file for 'encrypted-dns'
+pkgname=encrypted-dns
+version=0.9.13
+revision=1
+build_style=cargo
+makedepends="libsodium-devel"
+short_desc="DNSCrypt v2 server with support for DNSSEC and DoH forwarding"
+maintainer="MeganerdNL <meganerd@meganerd.nl>"
+license="MIT"
+homepage="https://github.com/DNSCrypt/encrypted-dns-server"
+distfiles="https://github.com/DNSCrypt/encrypted-dns-server/archive/refs/tags/${version}.tar.gz"
+checksum=5e4f9143313bf58888c31ec4e220e9fb65b28b60fe5b6aff872f9f2ecb7537d5
+system_accounts="_encrypted_dns"
+_encrypted_dns_homedir="/var/lib/encrypted-dns"
+mutable_files="/var/lib/encrypted-dns/undelegated.txt"
+
+if [ "$XBPS_TARGET_NO_ATOMIC8" ]; then
+	XBPS_CROSS_RUSTFLAGS+=" -latomic"
+	makedepends+=" libatomic-devel"
+fi
+
+case "$XBPS_TARGET_MACHINE" in
+	*-musl) makedepends+=" musl-devel libstdc++";;
+esac
+
+post_install() {
+	vlicense LICENSE
+	vinstall undelegated.txt 0644 var/lib/encrypted-dns
+	vsconf example-encrypted-dns.toml
+        vmkdir etc/encrypted-dns
+	touch ${DESTDIR}/etc/encrypted-dns/.placeholder
+	vsv encrypted-dns
+}

  parent reply	other threads:[~2023-08-04  9:37 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-02  5:14 [PR PATCH] " MeganerdNL
2023-08-02  5:28 ` [PR REVIEW] " classabbyamp
2023-08-02  5:28 ` classabbyamp
2023-08-02  5:28 ` classabbyamp
2023-08-02  5:28 ` classabbyamp
2023-08-02  5:28 ` classabbyamp
2023-08-02  5:28 ` classabbyamp
2023-08-02  5:35 ` MeganerdNL
2023-08-02 12:15 ` MeganerdNL
2023-08-02 12:16 ` MeganerdNL
2023-08-04  7:48 ` MeganerdNL
2023-08-04  9:33 ` [PR PATCH] [Updated] " MeganerdNL
2023-08-04  9:37 ` MeganerdNL [this message]
2023-08-04  9:40 ` [PR REVIEW] " MeganerdNL
2023-08-04  9:41 ` MeganerdNL
2023-08-04  9:41 ` MeganerdNL
2023-08-04  9:41 ` MeganerdNL
2023-08-04  9:42 ` MeganerdNL
2023-08-04  9:43 ` [PR PATCH] [Updated] " MeganerdNL
2023-08-04  9:59 ` MeganerdNL
2023-08-04 12:58 ` [PR REVIEW] " classabbyamp
2023-08-04 12:58 ` classabbyamp
2023-08-04 12:58 ` classabbyamp
2023-08-04 12:58 ` classabbyamp
2023-08-04 12:58 ` classabbyamp
2023-08-04 18:08 ` [PR PATCH] [Updated] " MeganerdNL
2023-08-04 18:17 ` MeganerdNL
2023-08-04 18:18 ` MeganerdNL
2023-08-04 18:22 ` MeganerdNL
2023-08-04 18:29 ` MeganerdNL
2023-08-04 18:41 ` MeganerdNL
2023-08-04 18:51 ` [PR REVIEW] " classabbyamp
2023-08-04 18:57 ` MeganerdNL
2023-08-04 19:01 ` [PR REVIEW] " MeganerdNL
2023-08-04 19:01 ` MeganerdNL
2023-08-04 19:20 ` classabbyamp
2023-08-04 20:52 ` MeganerdNL
2023-08-11  8:52 ` [PR PATCH] [Updated] " MeganerdNL
2023-08-11  8:53 ` MeganerdNL
2023-09-02 15:27 ` MeganerdNL
2023-09-02 15:31 ` MeganerdNL
2023-09-02 18:09 ` Duncaen
2023-09-02 19:12 ` MeganerdNL
2023-09-02 19:53 ` Duncaen
2023-09-02 22:11 ` MeganerdNL
2023-09-03 11:26 ` Duncaen
2023-09-03 11:26 ` Duncaen
2023-09-03 20:47 ` [PR PATCH] [Updated] " MeganerdNL
2023-09-03 20:57 ` MeganerdNL
2023-09-03 20:58 ` MeganerdNL
2023-09-15 10:08 ` [PR PATCH] [Updated] " MeganerdNL
2023-12-15  1:46 ` github-actions
2023-12-30  1:45 ` [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=20230804093713.L9r6Sa4fra20yfio_Dnvp6GSyujo-gm3Dgn_9dBb7yI@z \
    --to=meganerdnl@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).