On Tue, 10 May 2011, Yury V. Zaytsev wrote:
Is there a reason why we don't build 64-bit wine packages for RHEL6?
Apparently this is supposed to work [1], although, RHEL5- have gcc that
is too old, so the only possible target for now is RHEL6.
The 64bit wine is pretty useless at it is unable to run 32bit
applications. Unless that has changed recently ?
Or we could have the 64bit RPM package include a 32bit and 64bit wine
build ? Not sure what the recommended practice would be ?
Also, in what concerns 32-bit wine, is it possible to somehow add 32-bit
rpms to the 64-bit index for those who have 32-bit runtime installed? I
guess that's how EPEL does it.
The aim always was to create a tool that could check all the 32bit
packages for conflicts with the 64bit repository. And add all packages
from 32bit magically to the 64bit repository.
But I guess we could adopt the repository-scripts to whitelist certain
packages until we get around automating it ?
For now, I guess, if you want to install 32-bit wine, you need to add
rpmforge for i386 to yum.conf and be extra careful about it?
Yes, or simply download them manually :-/ Which is what I do.
The same thing people may want for flash. Since the 64bit flash plugin
could be vulnerable (which is uncertain, but not unlikely) people may want
to run a 32bit flash in their 64bit browser ?
--
-- dag wieers, [email protected], http://dag.wieers.com/
-- dagit linux solutions, [email protected], http://dagit.net/
[Any errors in spelling, tact or fact are transmission errors]
_______________________________________________
users mailing list
[email protected]
http://lists.rpmforge.net/mailman/listinfo/users
