Comment 4 for bug 640526

My own thoughts distilled after conversation:

  1. First document the manual build process for the Ubuntu Font Family by DM
  2. This gives a complete list of the software used for (1)
  3. Which leads to list of input/config files necessary to replicate (2)

My understanding is that the font build/development process uses multiple steps. The equivalent for C would be: pre-process (gcc -E), then compile (gcc -S), then assemble (-c), then link. If people start editing the assembly then any changes will be overwritten when starting the build process higher up the stack, and we've probably got the same situation with the multiple programs in the font stack.