[throwaway64]

Steam has a package so dependancies can be satisfied easily without resorting to "install xyz beforehand", and it runs an installer into your home folder because the user has to be able to modify the games directory for many, many games on steam, because stuff like configuration, custom maps, custom models etc, is stored alongside everything else.

Also steam has diff based patching (which requires accress from whoever is running the steam binary) which makes a lot more sense than how package managers operate for large packages, imagine downloading an entire 20 gig game every time there was a minor bugfix, it would be very obnoxious.

Unless the design of both package managers, and how steam games store settings/etc both change radically, this really is the only workable solution.

Luckily, you will still be able to share steam folders cross user, just simply give both users read/write access to the folder.

[StavrosK]

This is irrelevant. They can add the Steam binary to their own PPA and update it as they update the client now. Steam will be able to do all those thing, like every single program in Linux can, while being installed as a system package.

The way they're doing it now is plain unclean.

[throwaway64]

how is it irrelivant? if people are wanting games and stuff to be distributed through the package manager, all these issues very much apply.

Even the steam client package itself is something like 100megs, so it becomes painful without diff/delta patches. (steam updates a LOT)

[StavrosK]

I'm only talking about handling Steam updates, I agree with you on game updates. However, the Steam client can still access the user's home directory and create/access game data there, as all Linux apps do, so the current way of having Steam dump its binaries at the home dir is unclean.

Pretty much the only valid point is having to update the whole thing every release, but I've never seen the Steam client download an update that was less than 75 MB.

[throwaway64]

the issue is, if you have a cluster of games/etc managed by steam in your home directory that is already not under the control of package management, what do you gain by splitting out the steam client itself? it is easier from valve's perspective to just allow steam to manage its own updates along with everything else it manages, than to have a rather arbitrary split that gives you no real advantages anyways.

Steam has always been designed on both osx and windows to be a portable folder that you can move around from system to system and run stuff out of wihout worrying about installers and dependancies.

[StavrosK]

By that reasoning, if you have one package on your system that's not managed by the package manager, you should discard the package manager entirely.

The more packages managed by the system, the better. Ideally, you'd want the games, too, but I understand why Valve might not like that.

Using the unclean alternative when there's a clean one that's just as good isn't a good decision, in my opinion.

[Garoof]

"By that reasoning, if you have one package on your system that's not managed by the package manager, you should discard the package manager entirely."

No?

Something like "I want to play TF2, so I should update Steam and TF2" is a reasonably common thing and it makes sense to want one thing to handle both of them.

"You should discard the package manager entirely" does not follow from that.

[drivebyacct2]

> if you have a cluster of games/etc managed by steam in your home directory that is already not under the control of package management, what do you gain by splitting out the steam client itself?

The same thing you gain from every other linux package that has a globally installed application with per-user configuration? which is... every single other application in the entire linux world?

>Steam has always been designed on both osx and windows to be a portable folder that you can move around from system to system and run stuff out of wihout worrying about installers and dependancies.

Huh? Are you familiar with Linux? You can move/copy your home dir, reinstall the package-managed binary and it "just works". That is the best definition of portable, far better than copy-pasting a "Program Files" directory between machines and crossing your fingers. Again, I've yet to hear a technical reason that we can't have /usr/bin/steam and ~/.steam/<steamapps> like every other Linux application does.

[drivebyacct2]

>Steam has a package so dependancies can be satisfied easily without resorting to "install xyz beforehand",

This isn't even true. The deb has dependencies just like any other DEB you'd get through apt-get. That's... kinda the point of package management...

[eikenberry]

No. He means using a deb with a packaging system will install those dependencies automatically. Otherwise it would be the instructions to manually 'install xyz beforehand'.