I'm starting to prepare for the armv7hl koji builders... a few thoughts:

- I don't think we can have builders that do both armv5tel and armv7hl,
because the mock environment is populated with packages from outside the
chroot (i.e., mock populates the directory and then does the chroot).
Thus, any scriptlets will execute in the wrong environment. This should
be a rare occurrence, but since hardfp and softfp happily link together
and *do the wrong thing*, we need to avoid this scenario.

- We haven't planned to do multiarch for arm, but it might be desired in
some contexts, particularly if proprietary software is available only
with a particular ABI (e.g., Flash in softfp only?). Multiarch might
also permit builders to do both armv5tel and armv7hl. I think the cost
(effort, storage space) probably outweighs the benefits but the
discussion is worthwhile.

- It would be really nice to get ld patched so that attempting to link
hardfp and softfp would produce an error, instead of silently producing
undefined results.

- I'd like to build F15 on both armv5tel and armv7hl at the same time,
i.e., submitting to a.k.fo.o with a target of dist-f15 will kick off a
build on both variants by default (like 32-/64-bit builds on other
archs). To this end, Paul Whalen is looking at putting together an
armv5tel seed package set that matches the emerging armv7hl seed package
set as closely as possible.