From: cinerea0 <cinerea0@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: dnscrypt-proxy: update to 2.1.5, move config file
Date: Tue, 15 Aug 2023 00:28:08 +0200 [thread overview]
Message-ID: <20230814222808.8xNqYx3eH9dDYV-H0o_IDw-mjCa-3CPdDUZ9k7mTNzs@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: 1044 bytes --]
New comment by cinerea0 on void-packages repository
https://github.com/void-linux/void-packages/pull/45595#issuecomment-1678167276
Comment:
Good news, configuration files that have been edited are not removed on package upgrade even when their `conf_file` entry has been deleted. The following will happen on upgrades:
* Users who haven't customized their `/etc/dnscrypt-proxy.toml` file will have it removed, and the new file from upstream will be installed at `/etc/dnscrypt-proxy/dnscrypt-proxy.toml`. If they're alright with the upstream defaults so far they won't notice anything has changed.
* Users who have customized their `/etc/dnscrypt-proxy.toml` file will keep their file, but the service will use the upstream default at `/etc/dnscrypt-proxy/dnscrypt-proxy.toml` the next time it starts. Hopefully they pay attention to the INSTALL message.
Manual intervention on the user's end could be completely avoided with a post-install script, but messing around with the system like that without a very good reason seems unwise.
next prev parent reply other threads:[~2023-08-14 22:28 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 [this message]
2023-08-14 22:30 ` [PR PATCH] [Updated] " cinerea0
2023-08-24 16:49 ` cinerea0
2023-08-24 18:29 ` [PR PATCH] [Merged]: " Duncaen
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=20230814222808.8xNqYx3eH9dDYV-H0o_IDw-mjCa-3CPdDUZ9k7mTNzs@z \
--to=cinerea0@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).