has anyone thought of setting up an open standard for litestep built and module updating, like SharpE has? a system that includes a standardised build and module version check, and module name/version[/possibly download location). anyone would be able to set up a module repository using the standard, and the user could set what repository they want to use in an app/module's preferences.

it could be linekd into lsts by lsts holding information for each theme on what modules it uses. users could select which theme[s] to update, or to update everything

I thought about writing something that would grab something like loose-screw's recent module list and use that to update a set of *NetLoadModule lines. It would probably require NetLoadModule be changed to use a split name/version instead of the current combined method, but that's no big deal.

There would be a problem whenever a module changed how it worked in some fundamental way, like where the newer vers of mzscript don't load scripts from step.rc by default. You need to be able to tell people "here's what's changed" and allow them to choose whether or not to update. (haven't seen sharpe's system)