On Fri, 2023-03-17 at 09:18 +0100, Markus Volk wrote: > Am Fr, 17. Mär 2023 um 08:00:37 +0000 schrieb Richard Purdie > <[email protected]>: > > This changes the system layout to what systemd wants but what > > happens > > to sysvinit or anything else though? Some systems won't have > > systemd- > > tmpfiles and so on present. The commit message above makes it sound > > like systemd is the only thing that exists/matters. > > > I like systemd and I like that it standardizes a lot of things, but I > really don't care about politics. That's why I also sent a patch for > a different way. But the commit message is right, that would clearly > be a step towards systemd.
Regardless of what anyone thinks of systemd, I can't take patches which change existing behaviours if that change isn't explained, justified and documented. As such there is no way I could ever take a patch with the commit message in the current form since it doesn't mention anything about the impact on sysvinit, how to mitigate it (if needed) and what users should expect. I appreciate you likely don't care about sysvinit and don't want to spend any time on that. That is fine, I do understand. Equally, as the maintainer for OE-Core, I do have to care and I just can't take a patch like this. I just want to make it clear why it isn't something I can even consider in the current form and to make any change like this, we'd need more insight into the other impacts (e.g. busybox init too). It would help me if adverse effects are mentioned in commit messages. In this case I can spot it easily enough but I don't always know/spot all the issues. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#178749): https://lists.openembedded.org/g/openembedded-core/message/178749 Mute This Topic: https://lists.openembedded.org/mt/97667591/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
