Holly Bostick ha scritto:
Don't know if understud fully, but if you were suggesting to add ~x86 instead of ~amd64 ...Jan Callewaert wrote:
* Bastian Balthazar Bux <[EMAIL PROTECTED]> [2005-01-18 13:06:13 +0100]:
Recently kde 3.4 beta 1 appeared in portage tree,
there is a big change, they are now splitted in many single application ebuilds.
But they are all masked and keyworded ~x86,
since I want to try them on amd64 how can I keyword them all ?
hint: /etc/portage/package.keyword dont work for me
tia francesco
-- [email protected] mailing list
It has to be /etc/portage/package.keywords with an s
Jan
Not quite sure how/if that will help since ~x86 is not the keyword for ~amd64.
Are the packages even available for that arch?
Holly
well it work, the package is now installable, my worry is that adding that also enable x86 specific optimization and assembler code probably not supported from amd64.
If package.keyword is only used as a semaphore and the arch is not added to use flags it should be ok.
Well, of course it's added to the relevant section of /etc/make.conf, at least for the purposes of this emerge. After all, if "x86 specific optimization and assembler code" was not part of the package, there would be no need to separate packages by arch. At least that's how I see it.
So basically, you'd be installing the 32-bit applications, which might be OK (I don't have a 64-bit CPU), but I don't know if programs using normal 32-bit *emulation* for amd64 fall under amd64 or x86, and if under amd64, whether there is any conflict between "real" x86 and amd64 32-bit emulation.
So that's why I'd be questioning installing the x86 version, especially for something so big as KDE, even more if there was an amd64 version available or pending.
Holly
-- [email protected] mailing list
