Mike Arthur posted <200604201612.50223.mike@...>, excerpted
below, on Thu, 20 Apr 2006 16:12:50 +0100:
> I won't be turning off IA32 emulation, still need 32-bit
> packages, just rather manage them myself in the chroot.
OK. /That's/ what you meant in the part of the OP I didn't quite follow!
> Is there any ETA/plans for a multi-arch portage working, i.e. merging
> 32-bit and 64-bit non-bin packages with portage.
It has been on the list for some time, but no ETA that I'm aware of yet.
FWIW, portage-2.1 is on the way (regularly updated pre's in ~arch for some
time now, talk of an rc on the way), with the new features that have been
getting all the work (better security/signing, a portage API level that an
ebuild can set to tell portage that it needs to be at least that level to
properly handle the ebuild, better cache and metadata management, cleaner
and more modular code, and confcache, to name some of them).
In particular the portage API level thing will allow faster portage
development without having to wait nearly a year to be sure everyone has
upgraded from their old and incompatible versions before the old code can
be safely removed from the tree and portage. The goal is to then speed up
portage development, with faster releases every few months. One of those
releases will probably introduce multi-arch tracking. However,
successfully implementing it has some serious complexities (I didn't
appreciate how complex proper dependency resolution can be until I joined
the portage-dev list and started reading -- I have some /serious/ respect
for the code hackers that dare to tread that way, now, and that's just
for a /single/ arch/abi!), and it's not going to be an easy job. I expect
we're still looking at 8 months to a year out, before it'd be anywhere
close to stable. That assumes a portage hacker gets seriously interested
in the problem, as well. If not, it could be longer, tho it'll likely
OTOH, as time progresses, the need for it will become less urgent, as more
and more stuff will be available for the now default 64-bit platform. At
this point, that's already the case for most open source stuff, with a few
exceptions such as Open Office. With MS now onboard the 64-bit bandwagon,
even if they /are/ a year or so behind, in a couple years most of the
slaveryware closed source stuff like games and codecs will be available in
64-bit as well. Thus, ironically, we'll probably be finally getting
multi-arch package manager support, just as it's no longer really needed.
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
firstname.lastname@example.org mailing list