features module

Would it be a good practice to store omega sub-theme settings inside a feature using the features module? From what I can see, all the settings can be stored inside the .info of the subtheme using omega tools. We are building a pretty huge website right now and are looking for the best practices in link with the omega framework.

Any tips and advice on this topic would be much appreciated.

Hello,

I am looking to create meta package/module using http://drupal.org/project/features it's will contain mostly dependencies and basic settings I'll add to *.install due to some limitations of strongarm, etc.

So, the only component my feature have is some dependencies and therefor my *.info file does not contain any "feautres[][]=" generated which cause it to treat as regular module(not displaying under features list).

Well, from one side that's seems correct, no features = module, but this is mostly because of limitation and I still would like to treat it as feature.