[users] 64-bit wine packages

[Yury V. Zaytsev]

Hi!

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.

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.

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?

[1]: http://wiki.winehq.org/Wine64

[Dag Wieers]

Post by Yury V. Zaytsev
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 ?

Post by Yury V. Zaytsev
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 ?

Post by Yury V. Zaytsev
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 ?

[Yury V. Zaytsev]

Post by Dag Wieers

Post by Yury V. Zaytsev
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 ?

As far as I understand, it is supposed to work now, but is considered to
be of beta-quality (see [1]).

Post by Dag Wieers
Or we could have the 64bit RPM package include a 32bit and 64bit wine
build ? Not sure what the recommended practice would be ?

Apparently yes, but as far as I understand this will be deprecated as
soon as WoW64 is declared stable. Not sure if we should go this way, so
only do WoW64 (again, see [1]).

[1]: http://wiki.winehq.org/Wine64ForPackagers

Post by Dag Wieers

Post by Yury V. Zaytsev
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.

Oh yeah, this sounds a lot like the promised lands. So is there any
progress on this, does such tool exist already?

Post by Dag Wieers
But I guess we could adopt the repository-scripts to whitelist certain
packages until we get around automating it ?

I was just asking triggered by a request on IRC, I'm not prepared to
give any help of this :-(

Post by Dag Wieers

Post by Yury V. Zaytsev
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.

Ok, I see, then my advice did make sense.

[Yury V. Zaytsev]

Post by Dag Wieers

Post by Yury V. Zaytsev
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 ?

As far as I understand, it is supposed to work now, but is considered to
be of beta-quality (see [1]).

Post by Dag Wieers
Or we could have the 64bit RPM package include a 32bit and 64bit wine
build ? Not sure what the recommended practice would be ?

Apparently yes, but as far as I understand this will be deprecated as
soon as WoW64 is declared stable. Not sure if we should go this way, so
only do WoW64 (again, see [1]).

[1]: http://wiki.winehq.org/Wine64ForPackagers

Post by Dag Wieers

Post by Yury V. Zaytsev
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.

Oh yeah, this sounds a lot like the promised lands. So is there any
progress on this, does such tool exist already?

Post by Dag Wieers
But I guess we could adopt the repository-scripts to whitelist certain
packages until we get around automating it ?

I was just asking triggered by a request on IRC, I'm not prepared to
give any help of this :-(

Post by Dag Wieers

Post by Yury V. Zaytsev
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.

Ok, I see, then my advice did make sense.

[Yury V. Zaytsev]

Post by Dag Wieers

Post by Yury V. Zaytsev
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 ?

As far as I understand, it is supposed to work now, but is considered to
be of beta-quality (see [1]).

Post by Dag Wieers
Or we could have the 64bit RPM package include a 32bit and 64bit wine
build ? Not sure what the recommended practice would be ?

Apparently yes, but as far as I understand this will be deprecated as
soon as WoW64 is declared stable. Not sure if we should go this way, so
only do WoW64 (again, see [1]).

[1]: http://wiki.winehq.org/Wine64ForPackagers

Post by Dag Wieers

Post by Yury V. Zaytsev
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.

Oh yeah, this sounds a lot like the promised lands. So is there any
progress on this, does such tool exist already?

Post by Dag Wieers
But I guess we could adopt the repository-scripts to whitelist certain
packages until we get around automating it ?

I was just asking triggered by a request on IRC, I'm not prepared to
give any help of this :-(

Post by Dag Wieers

Post by Yury V. Zaytsev
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.

Ok, I see, then my advice did make sense.

[Yury V. Zaytsev]

Post by Dag Wieers

Post by Yury V. Zaytsev
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 ?

As far as I understand, it is supposed to work now, but is considered to
be of beta-quality (see [1]).

Post by Dag Wieers
Or we could have the 64bit RPM package include a 32bit and 64bit wine
build ? Not sure what the recommended practice would be ?

Apparently yes, but as far as I understand this will be deprecated as
soon as WoW64 is declared stable. Not sure if we should go this way, so
only do WoW64 (again, see [1]).

[1]: http://wiki.winehq.org/Wine64ForPackagers

Post by Dag Wieers

Post by Yury V. Zaytsev
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.

Oh yeah, this sounds a lot like the promised lands. So is there any
progress on this, does such tool exist already?

Post by Dag Wieers
But I guess we could adopt the repository-scripts to whitelist certain
packages until we get around automating it ?

I was just asking triggered by a request on IRC, I'm not prepared to
give any help of this :-(

Post by Dag Wieers

Post by Yury V. Zaytsev
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.

Ok, I see, then my advice did make sense.

[Yury V. Zaytsev]

Post by Dag Wieers

Post by Yury V. Zaytsev
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 ?

As far as I understand, it is supposed to work now, but is considered to
be of beta-quality (see [1]).

Post by Dag Wieers
Or we could have the 64bit RPM package include a 32bit and 64bit wine
build ? Not sure what the recommended practice would be ?

Apparently yes, but as far as I understand this will be deprecated as
soon as WoW64 is declared stable. Not sure if we should go this way, so
only do WoW64 (again, see [1]).

[1]: http://wiki.winehq.org/Wine64ForPackagers

Post by Dag Wieers

Post by Yury V. Zaytsev
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.

Oh yeah, this sounds a lot like the promised lands. So is there any
progress on this, does such tool exist already?

Post by Dag Wieers
But I guess we could adopt the repository-scripts to whitelist certain
packages until we get around automating it ?

I was just asking triggered by a request on IRC, I'm not prepared to
give any help of this :-(

Post by Dag Wieers

Post by Yury V. Zaytsev
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.

Ok, I see, then my advice did make sense.

[Yury V. Zaytsev]

Hi!

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.

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.

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?

[1]: http://wiki.winehq.org/Wine64

[Dag Wieers]

Post by Yury V. Zaytsev
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 ?

Post by Yury V. Zaytsev
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 ?

Post by Yury V. Zaytsev
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 ?

[Yury V. Zaytsev]

Hi!

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.

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.

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?

[1]: http://wiki.winehq.org/Wine64

[Dag Wieers]

Post by Yury V. Zaytsev
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 ?

Post by Yury V. Zaytsev
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 ?

Post by Yury V. Zaytsev
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 ?

[Yury V. Zaytsev]

Hi!

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.

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.

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?

[1]: http://wiki.winehq.org/Wine64

[Dag Wieers]

Post by Yury V. Zaytsev
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 ?

Post by Yury V. Zaytsev
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 ?

Post by Yury V. Zaytsev
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 ?

[Yury V. Zaytsev]

Hi!

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.

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.

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?

[1]: http://wiki.winehq.org/Wine64

[Dag Wieers]

Post by Yury V. Zaytsev
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 ?

Post by Yury V. Zaytsev
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 ?

Post by Yury V. Zaytsev
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 ?