Hi Florian,

I know the little restrictions (like exclusivearch), but using
mock-utils' build-from-scratch powers, it's much better to
support the 'outside platform'.
I see that only what outside is - is the kernel and the
compiler flags. Each of the platforms (NSLU2, Sheevaplug,
HTC-MSM and TI-OMAP) needs special Kernels because they are
more or less types of complete Systems-on-Chip. The userland
is always the same and tuned for v5te - this is the interesing
thing to rebuild CentOS.
This platform is also 32-bit and little-endian, so it's not
far away from i386.
You're right with Fedora-arm, that's why I also started with
FC6-arm and let it convert to CentOS-5. FC-arm is very useful
to understand what the ARM specific patches are standing for.

I know that C5p is not binary compatible to anything - but
is is nice to have the rock-solid software for the new
platforms. (PowerPC-32 was much easier and I will probably be
there at LinuxTag 2010 - my G4 Mac (400MHz) has still CentOS
5.2 and is slowly turning to 5.4).

I've targeted the Python issue on ARM - there were branches in
the .spec which gone the wrong way. So I had to define macros
for the python package.

B.S.