Valve Beginning To Look At Steam Linux Not On Ubuntu

[droste]

Do I need to do something with those folders too ?

usr ( bin, lib, share )

1. Download http://download.opensuse.org/reposit...2.3.1.i586.rpm
2. Extract the rpm with ark ( ark -a -b flash-player-11.2.202.238-2.3.1.i586.rpm )
3. Create folder /usr/lib/browser-plugins if it does not exist ( sudo mkdir /usr/lib/browser-plugins )
4. Copy libflashplayer.so from the extracted folder to /usr/lib/browser-plugins ( sudo cp usr/lib/browser-plugins/libflashplayer.so /usr/lib/browser-plugins )
5. Restart steam

Optionally 7. Remove downloaded and extracted filed ;-)

[Gps4l]

I manually downloaded the x86 package including the libflashplayer.so and copied it to "/usr/lib/browser-plugins/libflashplayer.so". This is with openSUSE but should be the same with other 64bit systems too (maybe the folder name changes to /usr/lib32/... or /usr/lib/mozilla/ or something like that).

I am on open suse 64 too, but it is still not working.


Do I need to do something with those folders too ?

usr ( bin, lib, share )

[Naib]

Works great here. A couple of minor bugs I need to report.

I would like systray support mind.

[henrymiller]

AFAIK, VMware ships their Workstation software as a large bundle with all libs included so it works cross-distro with no additional deps handling. I can see Valve doing the same for Steam.

[Adarion]

Now that is good news (besides the use of Flash) - and a good start for the coming year.

[droste]

Oh, I use 64-bit Ubuntu, hence I use 64-bit Firefox and 64-bit Adobe Flash Player.
Steam is 32-bit only?

Hence need to get the 32-bit Adobe Flash Player.
http://fpdownload.macromedia.com/get...ux.i386.tar.gz

I manually downloaded the x86 package including the libflashplayer.so and copied it to "/usr/lib/browser-plugins/libflashplayer.so". This is with openSUSE but should be the same with other 64bit systems too (maybe the folder name changes to /usr/lib32/... or /usr/lib/mozilla/ or something like that).

[newwen]

The beta has some bugs, I think.

There were some bugs on the input control when registering a new account where the carret in the textbox would insert text in reverse. I.e typing "hello" appeared as "olleh".

The client uses Flash, I don't know how to get it to work.
Maybe they should use HTML5 <video> instead?

Copy libflashplayer.so (32-bit) to ~/.steam/steam/ubuntu12_32/plugins

[Morpheus]

Which formats are good and which are bad?

Is RPM better than .deb?

My last touch with RPMs was far back in the days of Mandriva 10.2, since then, I use Debian (mostly servers) and Ubuntu (+derivatives, on clients). So I won't get myself into the argument...

[maligor]

Which formats are good and which are bad?

Is RPM better than .deb?

Having spent some time (professionally) on MeeGo and the rpm system used in it, it seemed to me like the RPM was more susceptible to horrible database corruption than deb is. It could just be that I wasn't experienced in the use of the RPM, but the error messages it produced were definitely not very helpful.

RPM is however simpler to create packages for, aside from some silly staging requirements.

[Thetargos]

Some Steam shortcomings that I hope they work out:

Let me jump into the discussion...

I understand the reason why they decided to go with Ubuntu (and hence .deb), as it is the percieved most widely used distribution, and also it is the upstream to a bunch of derivative distributions, even though it might stem from Debian itself. I agree with what others have stated about LSB, and as such I do reckon that "as part of LSB it would make more sense to go RPM", however a few .rpm based distributions have had traditionally differences in how they name their packages, etc... The way I see the package manager and dependency resolution problem would be to instead of relying on the distribution's package manager (apt, yum, etc) to abstract the dependencies to individual files (i.e libstdc++-6.0.so <i686>) and parse them to package-kit which would then use the local package manager to locate the appropriate package to satify said dependency.

Moving towards a more distro/package manager neutral dependency management (the way I understand it, any way) would necessarily go through PackageKit.

As to the "best" way to install Steam, I don't see any problem with it being a self-contained archive installable somewhere in the user's home directory or through package manager, in the end the behavior is the same as say GIMP, Mozilla, wine and other products: Have the core libraries installed system-wide, and locally needed files locally (by means of the currently used ~/.local/share/Steam/ path for Steam), and in such a way even that it could behave like some games in such that in-app updates override the system-wide application version, if say the system package managed version is not in sync with the in-app version. Some games allow this in their /main/directory Vs ~/home/.game directories, making the necessary adjustments in the launcher scripts by use of checks to assess the system Vs user's home directory versions of the components (with 'if' or 'case' statements).