I am thinking this will need some additional changes in releaseme. Namely I think releaseme should grow a gem to expose its lib, otherwise we'll have to clone all the time. ALSO, the libs should be put in module to avoid conflict with regular CI tooling.

Limited implementation now running on kmenuedit. Working nicely.

Needs to have releaseme changed to be more gem-like so we don't have name conflicts and can nicely manage it.

l10n injection is now enabled for unstable and stable for frameworks+plasma repos. Best watch out for build failures. To wholly disable this in vcs_source_builder.rb remove prepend SourceBuilderL10nExtension from the builder class.

Still TBD:

• use relaseme as gem rather than ad-hoc cloning
• make sure subversion is in the core image rather than installing on-demand
• refactor source builder to support l10n without prepending the magic module
• possibly look into controlling thread level of releaseme, with its internal default threading we may hit our heads on connection caps against anonsvn
• possibly pass more context into container so we don't have to rely on the rugged gem to determine what the code repo URL is.
• possibly extend releaseme to support a resolution from git url, which is what we need but currently we kinda cheat by pretending the repo_name == project_name, which isn't technically assured