Customizing config files for the user's home directory

[mister-drgn]

Unless I'm missing something, I'm not seeing a precedent for providing config files that go into the user's home directory. For example, suppose I want to customize ~/.config/touchegg/touchegg.conf. It seems like such files could go into (to use the proposed new file scheme) /usr/share/ublue-os/firstboot, and then the firstboot script could copy them over.

Or is there some other preferred way to handle this sort of thing?

EDIT: On second thought, this particular case might be better handled by updating the default config file in the usr directory, /usr/share/touchegg/touchegg.conf. But there might be other cases where one would want to copy files into the home directory, for example changing the settings for flatpak apps.

[bsherman]

You won't see much related to user-specific changes in the main or nvidia images built in ublue, as those try to stay pretty close to stock features/functionality of upstream Silverblue/Kinoite, mostly adding hardware enablement and auto-upgrades.

For an example of how to do some custom stuff per user, take a look at the bluefin repo.

There, there is an example of:

• setting default gnome settings for the whole system using dconf
• first-time boot run of yafti to install flatpaks and do other operations per user (and auto re-reun of that tool if its config changes)
• the method to run yafti uses profile.d and .config/autostart, so those are good hooks to setup almost anything for a user potentially.

[mister-drgn]

Thanks. I previously copied bluefin's yafti setup for the cinnamon image, so yes, my thought was to use its autostart to install items in the home directory. However, since I can overwrite /usr/share/touchegg/touchegg.conf without touching the home directory, I probably would only write to the home directory in a custom image, not in the base cinnamon image.