I'm trying to clean up my omega 4 sub-theme output.

Got SASS working nicely and outputs files as expected to for example:
/sites/all/themes/MYTHEME/css/MYTHEME.styles.css

However, I'm still seeing a stack of base theme files being pulled in like so.

/sites/all/themes/omega/omega/css/modules/system/system.menus.theme.css
/sites/all/themes/omega/omega/css/modules/system/system.messages.theme.css
/sites/all/themes/omega/omega/css/modules/system/system.theme.css

I think I understand that those support the base theme workings etc. But what is a good way to get rid of the omega references from the output?

I've done stylesheets[all][] = css/modules/system/system.base.css in MYTHEME.info file. But there are too many omega css files to specify one by one. a Wildcard would be good.

OR
Is there some better why to get them renamed and included in my sub-theme.

--I know aggregation with eventually pull them out, but I'm trying to get my head around the concept of not having to have omega and the sub-theme installed. (yes, I know it's a sub-theme, but imagine you can SASS all the required files into the subtheme and thus be standalone. Then at upgrade you just recompile of dev machine with new omega files).

Comments

Anonymous’s picture

Anonymous (not verified) CreditAttribution: Anonymous commented

You might want to take a look at hook_css_alter function which might suite perfect for your needs.
hook_css_alter

pietpomp’s picture

pietpomp CreditAttribution: pietpomp commented

Thanks hansulo, but you suggestion would still involve listing all the files specifically, except that now there is greater room for error in the function code than just adding lines to the theme.info as I described.
Unless I miss-understood you reply.