From your use-case description, and a cursory review of the code, it looks to me like you are trying to solve the same thing that patterns currently does.
Patterns is currently pretty stable, and supports a whole heap of Drupal config processes, not just enabling modules and blocks, but configuring users, settings, menu items, cck, views and nodes through (what looks like) a very similar API to the one you are starting to build.

I think it would be great if you looked at making some suggestions about how you think things could/should be done and joining the 'patterns' team.

Comments

dman’s picture

dman commented

Patterns FAQ in the handbook

bobooon’s picture

bobooon commented
Status: Active » Closed (works as designed)

Patterns is great for your typical configuration. However this project was developed to handle any case and is intended for those with PHP knowledge as a developer tool. In the Release module you are able to use the full PHP library to perform different functions, not just configurations. For example you can write a script that can convert aggregation feeds into feedapi nodes. Eventually I do plan on expanding the built in functions so less re-inventing has to be done but I think this is still useful for a handful of us that like to do it the more manual way.