From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: dnscrypt-proxy: update to 2.1.5, move config file
Date: Thu, 24 Aug 2023 20:29:56 +0200 [thread overview]
Message-ID: <20230824182956.6BwbuilVUUfWdECh9MMXM3TM8OK8MuDUKBHOt-UdotM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45595@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]
There's a merged pull request on the void-packages repository
dnscrypt-proxy: update to 2.1.5, move config file
https://github.com/void-linux/void-packages/pull/45595
Description:
#### Testing the changes
- I tested the changes in this PR: **YES**
---
I'm using this as an opportunity to pick up where #34517 left off. `dnscrypt-proxy` installs all of its supplemental files (that it periodically refreshes from upstream) into the same directory as its main config file. Currently this is `/etc`, which means we get a bunch of ambiguously-named files like "relays.md" polluting that directory. This change would group all those files together, at the expense of users having to move their config files to the new location.
Other changes:
* The files previously being installed as documentation were actually examples, so they are now installed with `vsconf`.
* The `generate-domains-blocklist` python helper script is now installed.
* The log directory is no longer needed after the mass switch to vlogger (#42026), so it has been removed.
prev parent reply other threads:[~2023-08-24 18:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-14 2:26 [PR PATCH] " cinerea0
2023-08-14 2:47 ` [PR PATCH] [Updated] " cinerea0
2023-08-14 3:02 ` cinerea0
2023-08-14 22:28 ` cinerea0
2023-08-14 22:30 ` [PR PATCH] [Updated] " cinerea0
2023-08-24 16:49 ` cinerea0
2023-08-24 18:29 ` Duncaen [this message]
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=20230824182956.6BwbuilVUUfWdECh9MMXM3TM8OK8MuDUKBHOt-UdotM@z \
--to=duncaen@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).