From: ahesford <ahesford@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: fontconfig: move default configuration to INSTALL/REMOVE
Date: Tue, 11 Oct 2022 19:48:23 +0200 [thread overview]
Message-ID: <20221011174823.HNbXOdb-xWDsybrJnWvw_xhOKywEstl8k8kIm7rNJMw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-32794@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 933 bytes --]
There's a closed pull request on the void-packages repository
fontconfig: move default configuration to INSTALL/REMOVE
https://github.com/void-linux/void-packages/pull/32794
Description:
Encoding /etc/fonts/conf.d configuration symlinks in the package means that upgrades and installations will clobber existing custom configurations. In addition, removing any default configuration files would cause xbps-pkgdb to complain.
Managing default configurations in INSTALL/REMOVE allows custom configurations to persist through upgrades and removals. A guard file, /etc/fonts/conf.d/.autoconfig, serves as an INSTALL guard to prevent configuration modifications during upgrade. It also stores a list of the default configurations that will be removed when the package is uninstalled. This is an extension of an idea from @ericonr.
These scripts should mimic existing behavior through the first subsequent upgrade or installation.
next prev parent reply other threads:[~2022-10-11 17:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 16:16 [PR PATCH] " ahesford
2021-09-01 16:29 ` Chocimier
2021-09-01 17:03 ` ahesford
2021-09-01 18:39 ` [PR REVIEW] " ericonr
2021-09-01 19:28 ` [PR PATCH] [Updated] " ahesford
2021-09-01 19:28 ` [PR REVIEW] " ahesford
2022-06-05 2:14 ` github-actions
2022-10-11 17:48 ` ahesford [this message]
2022-10-11 17:51 ` ahesford
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=20221011174823.HNbXOdb-xWDsybrJnWvw_xhOKywEstl8k8kIm7rNJMw@z \
--to=ahesford@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).