It would be nice if all the linux games listed all their dependencies on the store page (and better yet, on your game shelf after buying them). As it stands, most do but some do not (Tetrobot did not at first).

I don't care if the emphasis stays on the popular distros. Just do this:

Specify if the game has tarballs or not.

I've noticed that some games a friend purchased, for a non-supported Linux, don't have tarballs, while others do. Perhaps it's an error, maybe it isn't, but more clarity would help on this issue.

Are tarballs guaranteed in addition to the Ubuntu/Mint installers when a new game is released?
- If not, it would be good to know if a tarball is upcoming or still in development, too.

Don't get me wrong, I appreciate that an attempt to do Linux gaming was made, GOG is awesome for even being brave enough to try. I'd like to know what software I'm buying before I actually buy it.

The official Linux press release mentioned that tarballs would be available, yet only Ubuntu and Mint are mentioned in the main games search. Why not a third option for sorting by tarballs too?

It'll save a lot of angst to make these things more apparent to every Linux gamer. As well as increase the likelihood of more customers who use other distros.

Which games don't have tarballs? Regardless, the tarballs are only supported on Ubuntu and Mint.

There is a error for Flatout.

Flatout - Linux installer, English

It is a tarball in reality, although it states the opposite xD

I have a lil problem with Mark of the Ninja: Special Edition.

I've no problem running the base game, but when I extract and copy the tarball of the Special Edition the start.sh won't work. I changes the original start.sh for the Special Edition one in orden to play, but I do not get any Special Edition subtitle on the menus, so I don't know if I'm playing to it or not.

The base game is at 1.3v while the SE is at 1.2v, maybe that's the problem?

I just want to say that I really appreciate you work guys. I just bought Flapout 1& 2. I know that is a wine port, but game works perfectly. Port more games no matter for me if it is native or wine. If it works good then I am your customer :)

Once again thanks for Linux

Ok, then, thanks for getting back to me. If it's just an error, I understand. The tarball, I can do something useful with. :)

Would you guys ever consider doing a GoG humble bundle(if you haven't already)?
I personally think this would be a great way to get more people using the platform and it would support charities such as childs play and Electronic Frontier Foundation.

EDIT: Oh. I'm sorry. Didn't realize it said Linux FAQ. You can remove this now. ;(

I think it would be worthwhile to have a complete list of dependencies for those not running your typical flavor (site feature request, anybody?). I know these are early days for Linux games on GoG, but it's a relatively trivial change that would make things easier for many Linux users. Of course, I can appreciate why they might not want to get to this right away.

While it's nowhere near as common as with Wine, DOSBox does occasionally regress between versions (eg. there exist games that play better under DOSBox 0.72 than 0.74). That's why GOG always bundles a specific, tested version of it.

While Rabcor was a bit abrasive, he does have a point about PulseAudio so I have to at least partially agree with mptt's request for a more complete dependency list.

If you don't need audio hotplug, network streaming, or per-application volume control, dmix is a pretty reliably option these days and I still rip PulseAudio out of my *buntu setups because it still presents me with a new bug every time I give it a chance while dmix Just Works™.

(I think the most recent one was when playing a game in Wine caused pulseaudio to get stuck pegging one CPU core at 100% until it was killed and restarted.)

For people in my situation, it'd really be helpful to indicate in the system requirements when a game depends directly on PulseAudio rather than on something switchable with a PulseAudio backend like OpenAL or the client-side ALSA libraries.

(For example, when I got NightSky HD in a Humble Bundle, I had to play the Windows version in Wine because the Linux version would hang on a black screen when started and strace revealed it was waiting for a "successfully initialized" response from the PulseAudio daemon I's uninstalled.)
Given that, according to the URLs, GOG's system files tarballs under "patches", I get the impression that the naming issue with FlatOut and FlatOut 2 tarballs is a limitation in the site that GOG hasn't had time to fix. (eg. the main package for a game must be referred to as an 'Installer')

(That might also be why there's no GOG Downloader support for Linux games. Having giant "patch but not really" tarballs might be too confusing for it.)

Thanks, just checked it.
I doesn't seem to be a level called like that. Since I'm using a non-suported distribution I'll look into the start.sh for a solution myself. Thanks for your support Judas ;)