Is this also a good time to note that the amd64 and x86 could
*easily* be covered under the same keyword? We cover a large
variety of mips machines/userlands under one keyword, with
differences much more significant then that between x86 and amd64.
Sorry I disagree with this, differences exists and sometimes are a
problem. Some package and library don't compile cleanly under amd64 arch.
On few but existant cases it's good to have two different archs. Not
even going near the analizing the differences in the profiles.
So these things won't compile in a x86 chroot on a amd64 box even? I
find that really hard to believe. Besides, close collaboration between
folks with x86 and folks with amd64 installs can make it easy to ensure
the same versions work on both arches (if you really want to call them
separate arches...) Your profile argument is silly too, since both
arches could *easily* be merged into sub-profiles in our cascading system.
Besides, we have the same sorts of problems on mips, except they are
magnified since we have a possibility of 3 different userland ABIs, on
both big and little endian hardware. After dealing with this sort of
stuff for a long time with *far* fewer developers and time in general,
I'm really not impressed with your argument. You'll have to do better
then that.
-Steve
--
gentoo-dev@gentoo.org mailing list
