Re: [arch-general] systemd timers: switch default target to timers.target?

Thomas Bächler wrote in message <543579D1.4010902@archlinux.org>:

I don't care what upstream recommends, there is no reason for this target to exist and there is no reason to use it. Things get even worse, since you cannot order the unit After=something - since timers.target pulls the unit, it gets an implicit ordering Before=timers.target, removing lots of flexibility with regards to ordering (since timers.target is before sysinit.target).

I don't really care about timers.target, but shouldn't the dependency be put in the corresponding services files rather than in the timers? I personally see timers as similar to sockets files, essentially trivial to launch, all the work being done in the services files.