I tried deploying a Site Definition with a custom default.aspx page.
Within the <WebFeatures>
node of the Site Definition's Onet.xml I tried to reference a Feature which would get a web part manager of the newly deployed default.aspx page.
This failed.
Why does the Feature Receiver of a dependant feature get called BEFORE modules are deployed from a Site Definition?