Re: no systemd in containers: Requires -> Recommends

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>>>>> "RWMJ" == Richard W M Jones <rjones@xxxxxxxxxx> writes:

RWMJ> Couldn't it use inotify (or whatever we're using these days to
RWMJ> detect filesystem changes)?  So when you drop in the unit file,
RWMJ> systemd notices and reloads.

Well, the point is that systemd isn't running or even installed when the
daemons are installed.  The question is what happens when systemd comes
up later.  (And yes, systemd could use rpm file triggers so that we can
drop the scriptlets entirely.  That would be great, but it's an entirely
separate discussion.)

I know this thread has gone in a completely different direction, but the
original message was about modifying or removing the dependencies.  Can
we drop dependencies on systemd and still have a system that works as
expected if systemd gets installed later?  If so, then dropping the
dependency doesn't actually hurt anything since the kernel will still
pull it in, and thus the other arguments about this become kind of
pointless.

 - J<
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
http://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux