SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
At the moment there is only a Debian package available here
It's an Ubuntu Package. And I doubt, there will be any other option in the near future.
Quote:
Any ideas?
The Windows version runs fine on Slackware using wine. It sits in $HOME, doesn't need root access and touches nothing in /usr. A native Linux port should at least meet this standard.
It sits in $HOME, doesn't need root access and touches nothing in /usr. A native Linux port should at least meet this standard.
Why should an executable binary not reside in /usr? Why should an application with the purpose to install software on your machine not need root access? Why should an application that installs software on your machine not touch /usr? Do you have the same requirements for sbopkg?
It looks like the client fails to initialize on Slackware because it does not find pulseaudio... it also needs some magic to let it find a 32-bit libnss3.so on a multilib system, and a symlink in /usr/bin to /sbin/pidof so that the startup script can check for a running Steam client.
And since this is all 32-bit stuff I will have to create compat32 packages for pulseaudio and its few dependencies to try it out.
I will upload a rough steam package soon. I have no SlackBuild yet but I stuck a description of the commands to package the binaries inside its doc directory.
Too bad I entered "Other" instead of "Ubuntu" as the OS I am running... or else I might have gotten into that beta ;-)
I can't believe this day is actually here.. I haven't had a chance to download the .deb, and like AlienBob selected 'other' on my beta application so I think I'll be waiting a while.
Looks like a few hurdles to jump over, but nothing we can't sort out.. I'm really looking forward to playing first class games natively!
This is how I created a crude package - note that I run Slackware 14:
Code:
wget http://media.steampowered.com/client/installer/steam.deb
mkdir tmp-steam
cd tmp-steam
ar x ../steam.deb
cd -
mkdir package-steam
cd package-steam
tar xvf ../tmp-steam/data.tar.gz
mkdir install
cd install
tar xvf ../../tmp-steam/control.tar.gz
rm md5sums
mv postinst doinst.sh
cd -
mkdir -p usr/doc/steam
mv install/control usr/doc/steam/
mv usr/share/man usr/
makepkg -l y -c n ../steam-$(date +%Y%m%d)-i486-1alien.txz
I then created this symlink:
Code:
ln -s /sbin/pidof /usr/bin
And on a multilib system you need to have this variable exported in order to make Steam find the 32-bit seamonkey-solibs compat32 package:
And then of course, you will need pulseaudio and is dependencies speex and json-c, all of those are on http:/slackbuilds.org/
Note that before building pulseaudio, the README instructs you to create a "pulse" user and group:
But I'm afraid, this effort isn't going anywhere: Any Steam App available for Linux in the future will assume, that it will be executed on Ubuntu only and will fail miserably elsewhere. And as a Debian derivative, Ubuntu doesn't support LSB (which requires RPM) very well.
So we have 2012, when this is released it will be 2013, but I still have to infect my system with 32 bit libraries? And as if that wouldn't be enough they decided to make it dependent on the soundsystem with the highest latencies out there?
Wow, Valve, I thought you can do this better than that.
So we have 2012, when this is released it will be 2013, but I still have to infect my system with 32 bit libraries? And as if that wouldn't be enough they decided to make it dependent on the soundsystem with the highest latencies out there?
Wow, Valve, I thought you can do this better than that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.