UUID Migration

[nristock]

Mojang will probably move to a UUID based system for player names. Hence migration code is required to make sure banned players stay banned.

Possible solution: An upgrade routine will go through all player names and query mojang's DB for corresponding UUIDs - player names in our DB will be replaced by their UUIDs. Commands with player name parameters will internally translate them into UUIDs so we are only using UUIDs internally. Messages outputting player names will have to translate UUIDs into names. - Mojang will eventually implement bi-diretional lookups.

[joshuapaling]

Had a think about this. Just recording thoughts for my own future reference. We could basically make a really simple crappy copy of bundler's gem method, and do instance_eval on the gemfile, and if the second param is a string, figure out if the version requirement it specifies is already met by the version we have installed.

Alternatively, we could introduce bundler as a dependency and use the stuff bundler's already built in Bundler::Dsl to save us having to re-write the code ourselves. Will have a crack at implementing this later.

[thiagofigueiro]

Yeah, I suppose it's best to use the actual bundler code but, failing that, you could borrow the twiddle-wakka operator logic. I don't see an issue with adding bundler as a dependency - it's going to be there already anyway.

side-note: pessimize could make a good combination with safe_update. I'm going to give it a whirl as well.

side-note 2: found someone's implementation but didn't try it.