Timeline for Detect init system using the shell
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 7, 2011 at 7:40 | comment | added | beatgammit | @Caleb- Yeah, I already have that logic in there, but good catch. I was hoping for a way to sniff the init system to use an intelligent guess than a sane default. | |
| Aug 7, 2011 at 7:38 | comment | added | Caleb | @tjameson: I just realized I forgot the most important bit. This sort of thing is usually done with switches passed to the configure script. Each distro's build/package routines can call different switches, and your configure/make only has to know what switch it was passed, not detect all the possible software configurations. | |
| Aug 7, 2011 at 7:37 | history | edited | Caleb | CC BY-SA 3.0 | added 226 characters in body |
| Aug 7, 2011 at 7:34 | comment | added | Caleb | One installation script to rule them all is a BadIdea. It ends up failing more places than it works. Autoconf is good as far as it goes. Work hard on keeping your end of the software as generic as possible and include alternate init scripts in your package. Setup package specifications for several major distros. If your software is good you can get other people to help you out with getting it packaged for other systems. | |
| Aug 7, 2011 at 7:27 | comment | added | beatgammit | Hmph, so it's looking like I can't have a 'one script to rule them all' solution. I've seen a lot of programs that use autoconf or similar to handle cross-platform stuff, but it doesn't seem like it's the right tool for my application. Is maintaining versions for each platform really the only reliable solution? | |
| Aug 7, 2011 at 7:21 | history | answered | Caleb | CC BY-SA 3.0 |