Re: init script, installed but not activated

consequences. On the other hand, being the "universal" OS suggests that not only the most common use case should be considered. As a side-effect, this approach would allow creating packages such as "slapd-sysvinit", "slapd-runit" or "slapd-s6" if we wanted to support multiple init and/or service supervisor systems. -- Mat signature.asc Description: OpenPGP digital signature

Re: init script, installed but not activated

oth systemd and sysvinit, and each > init system will use the most capable dialect of startup scripts that it > understands, ignoring the others. I think that's a better model. Yes, this works too, and it looks like a good middle ground between high flexibility and keeping the number of tiny packages low. -- Mat signature.asc Description: OpenPGP digital signature

Re: Putting default config files in /usr [was; (newbie) Disruptive LIRC package update.]

ings on upgrade, and far fewer spurious conflicts. > > We do not have systemd for long enough to see the fallout of this bad > setup. > >> I would suggest that the problem here isn't moving defaults out of /etc >> into /usr, but rather the lack of widespread tools for managing that >> configuration. That's a fixable problem. > > Why do we cause problems in the first place so that we _have_ to fix > them later? > > Greetings > Marc > -- Mat signature.asc Description: OpenPGP digital signature