Data files in /etc

[slyon]

While packaging this project for Debian, I discovered that it is shipping many "conffiles" in /etc, which rather seem to be per-device data files and not supposed to be edited by a human operator. They have very generic names and are not properly namespaced, especially those:

-rw-r--r-- root/root      4486 2026-07-10 08:08 ./etc/plugin_manager.xml
-rw-r--r-- root/root     67705 2026-07-10 08:08 ./etc/usecaseKvManager.xml

Those files should likely move into their own namespace, e.g. under usr/share/audioreach/.

-rw-r--r-- root/root     27801 2026-07-10 08:08 ./etc/mixer_paths_GLYMUR_CRD.xml
-rw-r--r-- root/root     27377 2026-07-10 08:08 ./etc/mixer_paths_Kaanapali_MTP.xml
-rw-r--r-- root/root       239 2026-07-10 08:08 ./etc/mixer_paths_LEMANS_EVK.xml
-rw-r--r-- root/root     27801 2026-07-10 08:08 ./etc/mixer_paths_MAHUA_CRD.xml
-rw-r--r-- root/root       188 2026-07-10 08:08 ./etc/mixer_paths_MONACO_EVK.xml
lrwxrwxrwx root/root         0 2026-07-10 08:08 ./etc/mixer_paths_QCM6490_IDP.xml -> mixer_paths_QCS6490_RB3Gen2.xml
-rw-r--r-- root/root     26805 2026-07-10 08:08 ./etc/mixer_paths_QCS6490_RB3Gen2.xml
-rw-r--r-- root/root     27211 2026-07-10 08:08 ./etc/mixer_paths_SM8750_MTP.xml
-rw-r--r-- root/root     44449 2026-07-10 08:08 ./etc/mixer_paths_Shikra_CQM_EVK.xml
-rw-r--r-- root/root     44449 2026-07-10 08:08 ./etc/mixer_paths_Shikra_CQS_EVK.xml
-rw-r--r-- root/root      3810 2026-07-10 08:08 ./etc/mixer_paths_TALOS_EVK.xml
-rw-r--r-- root/root     27801 2026-07-10 08:08 ./etc/mixer_paths_X1E80100_CRD.xml
-rw-r--r-- root/root     27801 2026-07-10 08:08 ./etc/mixer_paths_X1E80100_EVK.xml
-rw-r--r-- root/root      4486 2026-07-10 08:08 ./etc/plugin_manager.xml
-rw-r--r-- root/root     22220 2026-07-10 08:08 ./etc/resourcemanager_GLYMUR_CRD.xml
-rw-r--r-- root/root     22226 2026-07-10 08:08 ./etc/resourcemanager_Kaanapali_MTP.xml
-rw-r--r-- root/root      6105 2026-07-10 08:08 ./etc/resourcemanager_LEMANS_EVK.xml
-rw-r--r-- root/root     22225 2026-07-10 08:08 ./etc/resourcemanager_MAHUA_CRD.xml
-rw-r--r-- root/root     10425 2026-07-10 08:08 ./etc/resourcemanager_MONACO_EVK.xml
lrwxrwxrwx root/root         0 2026-07-10 08:08 ./etc/resourcemanager_QCM6490_IDP.xml -> resourcemanager_QCS6490_RB3Gen2.xml
-rw-r--r-- root/root     22221 2026-07-10 08:08 ./etc/resourcemanager_QCS6490_RB3Gen2.xml
-rw-r--r-- root/root     22220 2026-07-10 08:08 ./etc/resourcemanager_SM8750_MTP.xml
-rw-r--r-- root/root     60467 2026-07-10 08:08 ./etc/resourcemanager_Shikra_CQM_EVK.xml
-rw-r--r-- root/root     11672 2026-07-10 08:08 ./etc/resourcemanager_Shikra_CQS_EVK.xml
-rw-r--r-- root/root      8474 2026-07-10 08:08 ./etc/resourcemanager_TALOS_EVK.xml
-rw-r--r-- root/root     22220 2026-07-10 08:08 ./etc/resourcemanager_X1E80100_CRD.xml
-rw-r--r-- root/root     22219 2026-07-10 08:08 ./etc/resourcemanager_X1E80100_EVK.xml
-rw-r--r-- root/root     67705 2026-07-10 08:08 ./etc/usecaseKvManager.xml

[qti-sbojja]

@quic-plai, do we need to maintain target specific files for these?
-rw-r--r-- root/root 4486 2026-07-10 08:08 ./etc/plugin_manager.xml
-rw-r--r-- root/root 67705 2026-07-10 08:08 ./etc/usecaseKvManager.xml

[slyon]

For Debian, being an universal OS, we will have a single package serving all targets. Therefore, if we need different files for different targets, we need to make all of the co-installable and available at runtime. Maybe each in their own namespace/target-specific directory.

The application then can/needs to decide dynamically which one to use.

Alternatively, we could make it a package configuration (e.g. "update-alternatives"), to symlink one "active" configuration to the specific target file(s) at package installation time (having some kind of target detection inside the package).