Tim writes:
Allegedly, on or about 5 November 2017, Sam Varshavchik sent: > Now, as I see it, this boils down to a one word, simple question: > > Why? > > Do we really expect that one should actually do that? > > Using privoxy as an illustrative example: is it really so > unreasonable to expect that installing a package called "privoxy", > and if this "privoxy" package requires all IP addresses to be up, > before it runs, then installing this package makes sure that this > actually happens, that it starts up after all network interfaces are > up? I tend to agree. But rather than thinking that a packet that requires a running network ought to start another waiting service to get it to wait for the right moment. Ought to depend on *that* waiting service, rather than listen to the wrong service.
You are proposing to modify each upstream package to inject custom code that will wait for all IP addresses to be configured, before proceeding?
And you think this is easier, and more maintanable, then simply fixing the broken systemd configuration just once, and not have to figure out whether or not each individual package requires this dependency, and be responsible for patching it, in perpetuity?
Attachment:
pgpyezqrReVdw.pgp
Description: PGP signature
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
