Installer Steam
Logg inn
|
språk
简体中文 (forenklet kinesisk)
繁體中文 (tradisjonell kinesisk)
日本語 (japansk)
한국어 (koreansk)
ไทย (thai)
Български (bulgarsk)
Čeština (tsjekkisk)
Dansk (dansk)
Deutsch (tysk)
English (engelsk)
Español – España (spansk – Spania)
Español – Latinoamérica (spansk – Latin-Amerika)
Ελληνικά (gresk)
Français (fransk)
Italiano (italiensk)
Bahasa Indonesia (indonesisk)
Magyar (ungarsk)
Nederlands (nederlandsk)
Polski (polsk)
Português (portugisisk – Portugal)
Português – Brasil (portugisisk – Brasil)
Română (rumensk)
Русский (russisk)
Suomi (finsk)
Svenska (svensk)
Türkçe (tyrkisk)
Tiếng Việt (vietnamesisk)
Українська (ukrainsk)
Rapporter et problem med oversettelse
At least that seems like a sensible place to put it.
What would be really nice is if they design that script in a way that makes it easy for users to write their own distro-specific installers. Then we can sort the ones Valve don't feel are worth the time/effort ourselves.
You can also check for steam's dependencies running this command on STEAM_DIR/ubuntu_32:
for file in *; do ldd ./$file | grep found; done
Hopefully Valve and Canonical aren't being bed buddies to exclude other distros...
Distro-agnostic isn't possible if they want to use the system's libraries, because Debian, Fedora and Gentoo all do dependency resolution differently. Then again, if the dependency installer script is only 15 lines, I'm sure we can sort it on other distros simply enough.
However, this isn't a permanent solution. The best probability would be for steam to become merged into the various repositories as it has been with Ubuntu, and let the repos manage the rest themselves.
The real solution is to have Steam be distro-agnostic. As long as a distro is standardized with Xorg, LSB, freedesktop.org, and other standards then that should be all that is needed and Steam should download any other libraries needed.
If distros want to provide some of those extra libraries themselves or doesn't want to ship with lots of missing libraries, they should:
1. Create an ACTUAL PACKAGE QUERY STANDARD for programs to query the package manager to pull some libraries with. I thought that the PackageKit project was this solution but I could be wrong and I'm not sure how far along they are with it.
2. #1 as well as make themselves compatible with a universal standardized package format so programs could call specific programs even more easily.
That could definitely work, but it would take some doing as far as I'm aware. I suppose if they checked for the more common package managers, (apt-get, yum, and pacman are the first to come to mine) and if none were found, and libraries were out of date or missing, it could grab them from the steam servers.
Personally, I prefer keeping most of my software confined to my package manager, as it makes updating and/or detecting conflicts much easier, but I can see the need for a more standardized "failsafe" for the sake of all non-standard distros.
Please feel free to correct me if I'm spouting nonsense or misunderstood you. Truth be told, I'm much more accustomed to Windows (mainly because of the distinct lack of games on Linux. I'm glad that's finally changing~)
If so then there isn't that much of a problem in my mind since the "package" is more of an installer so a standard .tgz package would most likely be best if they put out only one. That can be repackaged by the individual distros.
If we are talking about the dependencies for the games them self then no, most of that should be bundled with the games to minimize compatibility problems. Biggest problems is that different games may require different versions which may be incompatible with each other, and that different distros have different versions marked as latest stable.
Having Steam handle all of that for the games would create an environment which would be effectively the same as if they were bundled from the start, and it would put an unnecessary burden on Valve.