On Sat, Aug 3, 2019 at 5:33 AM Michael Ströder
On 8/3/19 9:50 AM, Neal Gompa wrote:
The only scenario in which you don't have systemd is if you're making a single application/service OCI container.
Yes.
But exactly this use-case is defeated by continuously adding dependency on systemd running in almost every package (e.g. replacing CRON with systemd-timer).
Well, a runtime dependency on systemd isn't necessarily required for packages shipping systemd units (including timers). They're just files... And in a container, service units and timers aren't really useful (same goes for sysv scripts and cron jobs). If we used %systemd_ordering instead of %systemd_requires, then containers won't be forced to include systemd if it's unneeded. It'd be even easier to drop that dependency in packages if the upstream systemd macros and triggers were actually used in the SUSE systemd package (*sighs*). But, that's a whole other can of worms... :( -- 真実はいつも一つ!/ Always, there's only one truth! -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org