Separation of packages poll

[darren]

Hey all,

I'm currently rewriting the config handling of cPGS, so that the "simple config" options one sees on the main page for each game's cPanel can be customized per user/game/install or left at the defaults (which can also be customized by the server admin.) During this process I've noticed it would be tidier if each Valve game was split into it's own package. For instance, rather than downloading a hl.cpgs full of DoD, CStrike, TF, etc, you would just download a hl_cstrike.cpgs , hl_dod.cpgs, hl_tf.cpgs, etc which would only install that one game. I'm not sure how useful having multiple options to switch from on the fly actually is, and there has been some concern over package sizes. So rather than make this decision myself, I'm going to post the question to you:

Would you rather have games broken down into their individual types or keep them in larger meta-packages ?

[Haaser]

This would probably be a major under taking, but if you are creating separate packages would it be possible to create mod packages. For example source mod.
Then if the client wanted a mod installed it could just be installed via cPgs? Just an idea.

[amccoy]

This would greatly increase the amount of work as there are several mods for every cpgs game

[darren]

Haaser - You can already create your own packages to be installed by default, including games with their mods already in place, however it still needs the startup command line edited (in almost all cases.)