meta dependencies but fire after a role

Hi,

Is there any mechanism like meta dependencies that allows me to fire a role after the main role has executed instead of before?

Currently I have to call the subsequent roles in every playbook. It would be much nicer if I could specify them in the role but have them executed after.

Technically these roles have a dependency on the main role but that would create some horrible chaining of roles.

An example is that I have an application role. It needs to have init.d, apache, config and a handful of other roles run. These should be run after the main one as they are dependent on rpms being installed etc.

Any help appreciated

James

I should add that we are stuck on 1.9.4

I should add that we are stuck on 1.9.4

Solved my own problem. Using a role that only contains meta dependencies works

Nice trick, thanks for sharing your solution.

Johannes