4 ms·
> let the user figure out how to support the three different init systems that can each be configured in seven different ways There's really only one init syst
by beojan 9y ago
> let the user figure out how to support the three different init systems that can each be configured in seven different ways
There's really only one init system you should care about anymore, and that's systemd. If you really insist on supporting old distros, you might also support /bin/init configured through LSB compliant initscripts. So that's two init systems, each with one way of configuring them.
The real solution, though, is to simply ship source code and let the distributions deal with this when they package it.
- api 9y ago(1) We still get "it doesn't work on upstart based Ubuntu" questions. Lots of these are still in use. (2) "When they package it" is when exactly? Our software is GPL and has existed for years and it's not in Debian, EPEL, or Fedora. We've tried to work with distributions to get our software in there. The experience is worse than the Apple Store, and that's saying something. I've been a Linux user since 1993 so I know all about the Linux community and how these things work. The processes in place made sense in 1998 but they have not scaled.
- beojan 9y ago1. Good point, that's what happens when Ubuntu decides to reinvent everything (upstart, Mir, Unity, ...) instead of using an existing solution. 2. What is your software? I'm not surprised about the RPM distros, which have always suffered from a lack of software in their repos, but with Debian have you tried filing an RFP (Request For Package) bug?