Code review comment for lp:~julian-edwards/launchpad/ppa-dependency-schema

Submitting to db-devel blank email FTW!

Ok, here's what I did:

= Summary =
Move a PPA's external dependencies from config to the database

A PPA can use external repositories for build dependencies. This was only
done for OEM Services as they have some dependencies that are not in PPAs.
The problem was that with the original implementation done via config items,
the LOSAs need to CP any changes and it turns out that OEM needs a few of
these per week.

So, the dependencies now come from a new database column which is only
editable on the PPA admin form so it's restricted to admins only. We don't
want anyone being able to set this as it breaks the promise that all the
source for a PPA binary is available in another PPA or Ubuntu.

To test, run:
bin/test -cvvt archive.txt -t archivedependencies.txt -t xx-ppa-workflow.txt

And you can see an example of admin page at:
http://launchpad.dev/~mark/+archive/ppa/+admin