Comment # 8 on bug 1224202 from Atri Bhattacharya

(In reply to Thomas Renninger from comment #7)
> Thanks Atri for looking into these details!
> 
> I'd concentrate on the 2 issues I mentioned in comment #3:
> 1. Systemd service conflicts must be made more obvious
> 2. TLP (or others) must not set any HW/systems parameters statically, e.g.
> at install time or when HW is (un-)plugged or similar. Setting up HW the way
> it is most convenient for the majority of the users is the job of the kernel
> or the kernel module serving the specific HW. So whatever TLP is setting by
> default (also all event driven things like what happens by default if
> USB/battery is unplugged or platform suspend or whatsoever) should be
> submitted to the corresponding kernel part and totally vanish from TLP.
> All user specifics which want to override these defaults can then go into
> whatever power/performance/... profiles getting activated via whatever
> service of whatever package...
> 
> I try to get 1. discussed with our systemd maintainer(s). It should be easy
> to get an additional syslog message mainlaine like:
> systemctl start tuned
>    ...
>    tlp service stopped to conflict with started tuned service
> 

I think that would be wonderful, and, in my opinion, sufficient. Many thanks.

For tlp specifically, I think because of its nature, we should only make it a
user-asked install — drop it from all patterns — and make it conflict with the
other two (p-p-d and tuned). I use it — and tlp-ui, which I also maintain —
myself, and it seems to me to be the best at what it does — reduce battery
usage on laptop, setup and disable charging thresholds, so on — but I would not
recommend anyone installing it without knowing what they are doing.