The one thing missing is that modules should be able to declare what other modules need to be enabled. I think I agree with Steven's basic premise that we don't want to auto-activate modules unless the operator says it's ok, so in my ideal world I'd come back with a list of modules that need to be activated and say "activate all these modules too?" kind of like yum does. I assume apt does roughly the same thing.
I think that's too much workflow: * user clicks checkbox. * user clicks submit. * user gets message listing pre-reqs. * user clicks all pre-reqs. * user clicks submit. * user gets more pre-req messages. I'd much rather see the pre-req's listed in the description: name | description (requires: comments) | [] [] Then when the user clicks the box, we *can* enable the pre-reqs without further user intervention, because we can assume he saw the required components part of the description, and still wants to continue. -- Morbus Iff ( you are nothing without your robot car, NOTHING! ) Culture: http://www.disobey.com/ and http://www.gamegrene.com/ O'Reilly Author, Weblog, Cook: http://www.oreillynet.com/pub/au/779 icq: 2927491 / aim: akaMorbus / yahoo: morbus_iff / jabber.org: morbus