I think the message here is that there should be a man page or alias to a man page for every event. As James says, that is being done with the upstart-events man page. So I think on that alone, this bug can be Confirmed and set to Wishlist. James, if there is another bug where you've been tracking the work, can you mark this one as a duplicate of it?
As far as the assertions, I think we have a method of making sure that required files are there in the packaging system. The package upstart, which owns /etc/init/rc-sysinit.conf, depends on mountall and ifupdown. Further, there may be situations where something starts on an event that is only generated by something it is not dependent on. For instance, you may only want to run task foo when a service with NEEDS_FOO=1 starts.
start on starting NEEDS_FOO=1
The loose coupling gained by *not* making things too rigid is I think part of the power of the system. The 'emits' keyword is sort of like assertions, but on the other side. Right now, there's no enforcement of emits, so they're prone to rotting over time. With the visualization stuff that James Hunt has been working on (its really, REALLY cool.. James, please get it out soon! :) You'll see that your event isn't pointed to by any 'emits', or that your job will point to an event that isn't consumed by anything.
I think the message here is that there should be a man page or alias to a man page for every event. As James says, that is being done with the upstart-events man page. So I think on that alone, this bug can be Confirmed and set to Wishlist. James, if there is another bug where you've been tracking the work, can you mark this one as a duplicate of it?
As far as the assertions, I think we have a method of making sure that required files are there in the packaging system. The package upstart, which owns /etc/init/ rc-sysinit. conf, depends on mountall and ifupdown. Further, there may be situations where something starts on an event that is only generated by something it is not dependent on. For instance, you may only want to run task foo when a service with NEEDS_FOO=1 starts.
start on starting NEEDS_FOO=1
The loose coupling gained by *not* making things too rigid is I think part of the power of the system. The 'emits' keyword is sort of like assertions, but on the other side. Right now, there's no enforcement of emits, so they're prone to rotting over time. With the visualization stuff that James Hunt has been working on (its really, REALLY cool.. James, please get it out soon! :) You'll see that your event isn't pointed to by any 'emits', or that your job will point to an event that isn't consumed by anything.