Technically there’s nothing that would prevent us from adding GOG Galaxy in non-free on x86 only – the package would just contain the Windoze version and a “Requires: wine” line in the spec…
Whether or not we want to do that is actually a valid question.
Obviously one reason to do it is that it would make stuff instantly available that isn’t available on other distros (and for some reason some people are scared of typing “wine something.exe” but not scared of running binary-only native applications – why? No difference at all…)
One reason not to do it is that we’d probably get endless requests for “package this Windows application the same way” (but if we can find volunteers to do it, actually, why not?)
Users please keep in mind that this is a development version using developer (Cooker) repositories.
Expecting everything to be trouble free is not realistic, there can be problems. Development release is for testing to discover and correct as many problems as we can. The ISO file says “OpenMandrivaLx.4.0-beta” for a reason.
There will be a repository split soon when we create repositories for OM Lx 4 and that will isolate users somewhat from the trauma of using something while developers are working on it. That will happen about the same time as we do our RC (Release Candidate) release. RC is last step before GA (General Availability) release. GA is the final or public release marking the release as “stable”.
I did not find the server slow, yesterday I downloaded ISO in few minutes.
All the development releases are only at ABF.
Once we’ll have RC out it will be available also at SourceForge, and maybe some alternative location too.
Yes it is easy. Be patient. Wait until everything gets fixed. You are using cooker repositories which are always in development. I have every confidence that the @AngryPenguin will get this working soon enough.
Edit: Problems like this usually just mean a package needs to be rebuilt for updated dependencies. Again, just wait until developers have a chance to do this. This is why we keep tying to explain to you and other users the nature of using cooker. Expect problems. If you are using cooker and you expect no problems you will be disappointed. And after OM Lx 4.0 is released this part changes and users are seperated from development process. (Basically after repositories are split.)
You need to enable the 32-bit repositories – steam is mostly a 32-bit application, and therefore requires all sorts of 32-bit libraries (like all the ones you listed).
I think openmandriva LX 4 its not so bad to be in beta, but lot packes is missing or not setup.
I also have issue with LX3 but its works better, but did not have updated packages than LX4.
Its it some bug issue list? So i know what is wrong with LX4 beta?
You need to enable the 32-bit repositories – steam is mostly a 32-bit application, and therefore requires all sorts of 32-bit libraries (like all the ones you listed).
I did not get answer about LX3, but i think i get error also with start steam.
So its more setup with openmandriva? Because its look like run steam runtime or diskspace error is a issue with openmandriva only, its works better with fedora\ubuntu or other distribution? Do you have idea why?
Steam can be started with steam, or if its fail, steam --reset
But how to find out why its not running? I guess operatingsystem, i find out that, Steam did not works, if i add fedora steam with dnf i still get same error message, so i think its because of LX 4 operatingsystem not repo or configuration.
So its most be something with operatingsystem that is wrong.