> > p.s. devuan forks rsyslog package, would your salsa MR for rsyslog > > make sense there? (can offer to forward MR to devuan maintainers if > > that would help devuan+runit people..) > > Sounds like moving the discussion to a bug on the Devuan BTS would be > a good idea. My preference would be to solve this in the fork > directly for runit or any other init rather than a drop-in.
Yeah but this pacakge has to work properly both in Debian and Devuan (and other downstreams too) and I'm not sure how this could be possible. Example: *devuan could change the /lib/rsyslog code and add runit support, but I still need the duplicate logrotate file for Debian (in this case rsyslog gets HUP twice, and you still get spam in logs) * devuan could change the logrotate file to work with fragments in /lib/rsyslog but I still need need the duplicate logrotate file for Debian (you only got spam in logs) Overall fixing in Devuan only works if there is a reliable way to identify a Devuan system in maintainerscript, so that I could make the copying of the logrotate file a no-op in Devuan systems..
