[unified] Use of /etc/chromium-flags.conf

[Eloston]

One thing that popped out to me on initial inspection of unified is chromium-flags.conf. Will this be overwritten on each package update? In regular Debian builds and unportable, we read files within /etc/chromium.d to avoid package updates from stomping over the user's changes.

[ghost]

It's because I switched to the launcher that we use over on Arch which just used a single file containing line terminated arguments to find arguments to append to chromium. I assumed dpkg / apt will automatically handle anything under /etc for backups. I only plan to change this file if there's some arguments we need to add by default. I'll test this later to see if it's actually an issue.

[Eloston]

So apt in interactive mode (the default) will prompt the user what to do about the user-made modifications to package files. That's why Debian modifies packages to use .d directories so that packages can introduce new flags and users can add their own flags without causing a conflict at install time.

I personally have some flags to change the Chromium cache directory and enable Wayland. Also, it'd be a smoother transition from users transitioning from older versions of our packages or the official Chromium packages.