Github messages for voidlinux
 help / color / mirror / Atom feed
From: github-actions[bot] <github-actions[bot]>
Subject: Re: [PR PATCH] [Closed]: dnscrypt-proxy: put config in subdirectory of etc/.
Date: Mon, 01 Aug 2022 04:14:33 +0200	[thread overview]
Message-ID: <20220801021433.eugBND7Fki4DIpuhC7ocoljyfBF8Jojda9keysvfZH4@z> (raw)
In-Reply-To: <>

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

There's a closed pull request on the void-packages repository

dnscrypt-proxy: put config in subdirectory of etc/.

this change prevents dnscrypt-proxy from polluting etc/ with lists of relays, resolvers, etc.

After enabling the service, I was seeing these files show up in etc/:

Not sure how it should notify that the config location has moved. Should there be an `INSTALL.msg`, or should the config be moved in post in an `INSTALL`?

<!-- Uncomment relevant sections and delete options which are not applicable -->

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

#### New package
- This new package conforms to the [quality requirements]( **YES**|**NO**

<!-- Note: If the build is likely to take more than 2 hours, please [skip CI](
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
#### Local build testing
- I built this PR locally for my native architecture, (ARCH-LIBC)
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - aarch64-musl
  - armv7l
  - armv6l-musl

      parent reply	other threads:[~2022-08-01  2:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13 20:36 [PR PATCH] " TinfoilSubmarine
2022-01-02 18:47 ` cinerea0
2022-01-13 18:22 ` [PR PATCH] [Updated] " TinfoilSubmarine
2022-01-13 18:25 ` TinfoilSubmarine
2022-03-24 23:37 ` TinfoilSubmarine
2022-03-28 21:05 ` daniel-eys
2022-07-18  2:13 ` github-actions
2022-08-01  2:14 ` github-actions [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220801021433.eugBND7Fki4DIpuhC7ocoljyfBF8Jojda9keysvfZH4@z \ \

* 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).