I see what you mean now... the same autobuilder can be used with just another target added, and the repository would contain a thumb compiled version along with x86 and armel versions.

I wonder though, how does apt-get know to install the thumb version over the normal armel version? We wouldn't want to break the repositories for those people who don't want to run thumb binaries (I suspect), or can't because they aren't running kernel-power. This is why I was thinking a separate repository for thumb-extras, testing and dev would be a possible solution. A user could enable these along with the regular extras repositories and get the thumb versions of applications if they exist (assuming the thumb versions have a higher version, or +thumb0 appended). I don't know enough about how apt-get or repositories work to know if that makes sense or not.

After that, I guess we'd have to look at making changes to the extras-assistant (and midgard?) to support thumb binaries as well. Perhaps that all falls into place by just adding a target to the existing autobuilder processes though.

Hopefully Freemangordon can speak to some of that, since I know he's had recent experience with the autobuilder and extras-assistant, or anyone else who understands repositories/apt.