From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Implicitly set conf_files
Date: Sat, 11 Jul 2020 08:16:47 +0200 [thread overview]
Message-ID: <20200711061647.tkpS2bg1HHBO48YuJg7dKvo9s8uMYRGkLDomG-nas4I@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21649@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/issues/21649#issuecomment-656991120
Comment:
AppArmor profiles aren't conf files either. They are in `/etc/apparmor.d/`, but the local files in `/etc/apparmor.d/local/` are conf files.
@Duncaen what do you think about making `/etc/runit/ctrlaltdel` a `conf_file`? It is something that a user can change depending on the action they want to trigger when they use that keyboard shortcut.
> Should /etc/sv/service/confcount as conf?
@travankor IMO yes, it's where we recommend users make changes that persist across package updates. I believe the `vsv` function marks those as conf by default.
How would this work for new applications that for some reason store files in `/etc` that aren't config files? Will we have a new `no_conf_files` or `no_auto_conf_file` field, or have to add exceptions to the script?
---
To keep track, stuff I can think of in `/etc/` that aren't conf:
- `kernel.d/`
- `os-release` ?
- some/most(?) of the stuff in `zfs/`
- `polkit-1/rules.d/50-default.rules`
next prev parent reply other threads:[~2020-07-11 6:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 11:02 [ISSUE] " Gottox
2020-05-05 11:12 ` Duncaen
2020-05-05 16:44 ` sgn
2020-05-16 14:02 ` Chocimier
2020-05-18 7:12 ` Gottox
2020-05-18 7:13 ` Gottox
2020-05-18 8:00 ` travankor
2020-05-18 8:00 ` travankor
2020-07-11 5:06 ` ericonr
2020-07-11 5:14 ` ericonr
2020-07-11 6:16 ` ericonr [this message]
2021-01-21 18:00 ` ericonr
2022-04-16 2:02 ` github-actions
2022-07-16 2:13 ` github-actions
2022-10-15 2:16 ` github-actions
2023-01-14 1:55 ` github-actions
2023-01-28 1:59 ` [ISSUE] [CLOSED] " github-actions
2023-01-30 18:47 ` Chocimier
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=20200711061647.tkpS2bg1HHBO48YuJg7dKvo9s8uMYRGkLDomG-nas4I@z \
--to=ericonr@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).