I'm working on a fairly large SharePoint 2010 project. We have broken up the code into a number of solutions, each containing a number of features which we deploy via powershell and activate in the target environment. So far so good.
However, the problem we now face is that because some features are dependent on others, we need to ensure they are activated in the correct order. At the moment we do this by having deployments done by someone who just "knows" what order to use and keeping the magic sequence in a team wiki.
However, we'd be much happier if we could automate the activations somehow. The idea we have come up with is a "feature activating feature" or "one feature to rule them all" which would give us a one click "activate all" function. The hope is that all we have to do is maintain this one feature and all of our subsequent deployments will have their features switched on in the right order.
My question is this - is this a reasonable thing to create or have we lost it? Is there a better way of ensuring that our feature constraints are met?