On Wednesday, March 20, 2013 11:59:23 PM Justin Karneges wrote: > So I'm considering two options: > 1) Create a "mongrel2" package with a disabled default config that does > not autorun. This would be similar to how the haproxy debian package works. > You install the package, but it doesn't actually run unless you tweak some > files. This way if mongrel2 gets pulled in as a dependency, no other > webservers break. > 2) Create two packages: "mongrel2-base" containing files/binaries only, > and "mongrel2" that depends on mongrel2-base and sets up a default config > with autorun. Apps like mine would depend on mongrel2-base only, ensuring > that if mongrel2-base gets dragged in as a dependency then nothing will > break. Users that want to use mongrel2 as their primary webserver can > install the mongrel2 package explicitly, resulting in an out-of-the-box > working instance similar to apache. > > I'm partial to the second option since it seems to be the best of all > worlds, but I'm not familiar enough with packaging to know if there's a > precedent of this sort of thing.
Found one: mysql. There is a package "mysql-server-core" that contains all necessarily files and binaries to run mysql, but without any default configs or startup scripts. Kmail depends on this package, and uses a private instance of mysql to manage email. To get an autorunned system mysql, then you explicitly install "mysql-server". Justin
