[development] Help fix Actions API - test the patch!

[fago]

> Webchick and I have built a patch that fixes this, moving the truly  
> core actions API functions into the .inc file, moving one setup  
> screen into system.module, and keeping the advanced hook-to-action  
> mapping UI in the optional actions.module. The patch also fixes a  
> number of schema related issues and code style problems that chx has  
> pointed out in the past.

If modules can't assign actions to hooks, what are modules supposed to
do with the actions API? Retrieve configured actions and fire them
theirself?

Sry for the probably dumb question, but I'd like to get this right.

thanks,
fago