Am 18.12.2015 um 15:44 schrieb Neil Horman:
On Fri, Dec 18, 2015 at 01:27:33AM +0000, Zbigniew Jędrzejewski-Szmek wrote:For some packages "reduced capacity" because of lack of systemd.rpm means "doesn't even get started as expected" or "crashes on start with permission errors" or "cannot write logs" or similar. Like Lennart and Neil said, utilities provided by systemd.rpm are the basis which allows many things to "just work". This is so obvious that it is assumed implicitly in this disussion, and it's hardly "personal use cases".I concur, this really seems like were forsaking full OS functionality to support a specific container use case, which is wrong. And the argument that its ok because the kernel will pull in systemd, while currently accurate seems like bad practice, as philisophically rpms always specify all their requires instead of assuming some other package will do it for them
no idea what you are talking aboutfollowing "as philisophically rpms always specify all their requires" than wahtever package has to have a "Requires: systemd" when it requires systemd and since that is not happening they all rely anyways that something else does it
so following your logic the change should be done in case there is no kernel installed and the packages in the container don't need systemd to have the ability to remove it
Attachment:
signature.asc
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
