mozilla/kuma — pull request #2869 by ubernostrum (2014-10-31 13:34:02+00:00)
Title: Fix bug 1057294: Eliminate kuma-lib

This is... large. There was no other way around it.

It also is going to require careful checking before we merge it, because, well, it's large, and it touches basically every dependency we have.

Some notes:

* Everything in this except for the very last commit is auto-generated. It turned out to be the easiest way; I have a bash script which does two clean checkouts of kuma; it does the surgery in one of them, and uses the other as a source of copiable static files (since quite a lot of what used to be kuma-lib is actually static full copies of things).
* As a result, it is a lot of commits. 118 of them at the moment. Consider this my impact-graph contribution for the quarter :)
* More seriously, it is a lot of commits because it's scripted and because I wanted to be able to check any step of the process and re-create the whole thing on demand. As such, there are begin and end commits for killing off the original `vendor/` and restoring the static files, and a bunch of commits in between to re-add all the submodules. It's two commits per submodule: one to re-register it, then one to update it to the commit kuma-lib was at.

Some things still to do:

- [ ] Hunt down every place in the install docs that refers to kuma-lib, and kill it.
- [ ] Obsolete this whole thing by pulling as much stuff as possible into pip-installed and peep-verified dependencies rather than submodules or static embedded copies. There are bugs for that.

Instructions for spot-checking:

* Hold on to your butts.