One needs to carefully watch the redistribution license for daemontools. Essentially, it cannot be distributed as a binary in an LSB-compatible form. Quoting DJB's FAQ:
"May we distribute binaries?
You may distribute a precompiled package if
* installing your package produces exactly the same files, in exactly the same locations, that a user would obtain by installing one of my packages listed above;
* your package behaves correctly, i.e., the same way as normal installations of my package on all other systems; and
* your package's creator warrants that he has made a good-faith attempt to ensure that your package behaves correctly.
All installations must work the same way; any variation is a bug. If there's something about a system (compiler, libraries, kernel, hardware, whatever) that changes the behavior of my package, then that platform is not supported, and you are not permitted to distribute binaries for it."
This borders on the ludicrous, since he INSISTS on a TOP LEVEL directory under /!
An RPM that meets LSB cannot be distributed, since the LSB will never allow /service to exist; meaning Red Hat etc will not distribute daemontools or virtually any other DJB tool. And DJB insists it MUST use HIS correct layout or you cannot distribute binaries, period. This is unacceptable to the various Linux distributors; and if a distributor is violating this DJB will try to shut it down, I'm sure.
I say that wearing my "PostgreSQL RPM maintainer" hat, so it's not like I've never built an RPM before (been doing it five years, in fact...)
The relevant standard (proposed; FHS 2.2 is current) is available online at http://www.pathname.com/fhs/pub/fhs-2.3.html
