So you guys introduced distro-agnostic installers, but don't want to support other distros.

You guys replaced deb/ tar.gz archives with a shell script + zip archive, but you don't support unpacked zip archives, but did support tarballs?

Zip archives are generated from the same sources as tarballs. Re-adding tarballs is not a problem at all. There's also no need to "support" tar.gz archives. I doubt anyone believed they were "supported" anyway. Hide that option and we are all happy again.

And here I'm still wondering when the Linux version of both Metro games are coming, I know the Mac one has issues but Linux seems pretty good: https://www.youtube.com/watch?v=f1JjWcbvupU


Regarding the thread topic:

To unpack the setups without installing, open a terminal and run: "unzip gog_gamename.sh'", the file unpacks in 3 folders named 'data', 'meta' & 'scripts'. The game's main data files can be found in data, the other 2 folders aren't needed to run the games.

I'm confused. As far as I can see anything unzipped has same structure in /data/noarch as installed stuff would, and all the scripts are available as source. As such I can't see a single issue with replacing tarballs, as I can still do everything manually if I so desire. The whole 'not supported' stuff is just legal safeguard.

So what exactly is the problem? If anyone wanted to make a different package or not run scripts they can do it themselves.

It's extra server space, extra bandwidth and if you really feel like just extracting the files, it shouldn't be too hard to do that. You get a little extra work, but the script has all the relevant information you need.

It's even possible to replace the script at the beginning of the file or use a 3rd party script to do the extraction for you. Once somebody does the work, that is. It wouldn't surprise me if somebody would do that just to be helpful.

I'm not really sure I see a problem here.

OTOH, it would be kind of nice if they handled it like AMD does. Have a script that can generate the appropriate package, but I have no idea how much work that is.
FWIW, this is almost exactly what I've been wanting since GOG announced that you'd be supporting Linux. Probably the only thing better would be if the script could generate a package for the specific platform.

But, I don't particularly think it's worth the effort. I know AMD does that with their driver packages, but it's a pain and I'm sure it would just add to the support questions.

For those that don't want to install normally, all you have to do is add --target directory and it will extract to that directory. Not really any different than what I was doing previously with those tar files.

There's also a --tar that allows you to access the tar data.

Unfortunately, the script seems to be broken and you can only access help by editing the file. Hopefully that's going to be fixed at some point.

just two little things:
there is too much license stuff in the EULA window. and it seems the GPL2 is included two times :)
just make a statement which parts of the setup use which license and provide a link where to read that license.
same as you do with the GOG User Agreement.
That would make that window a lot more readable.

The mojosetup uses the murrine gtk2 engine, which is not included in the default gtk2-engine package. So I see a lot of annoying (but harmless) error messages. Wouldn't it be better to use one of the standard engines that is installed everywhere?
that only extracts the mojosetup, not the game.

Using MojoSetup was a good call. Cheers!

There's some obvious bugs in the process that really should have been caught before releasing any of the games. For example the --help doesn't do anything other than print the version number of mojo setup. Whereas --info prints that information and some other stuff.

seems more a deliberate change than a bug from looking at the script ;)

besides you don't need any of that. just use unzip as somebody wrote earlier:

unzip <installer.sh> 'data/*' -d <target dir>

I like differential patches!

I dislike having to re-download everything to make use of them.

That's my problem, for some reason tar doesn't work and the internal commands they give you for working with the archive are badly broken.

And yes, I'm aware that this works, I was the one that pointed out that this is a typical script + archive file that's commonly used. I was just a bit surprised that tar wasn't working when the script was using tar.

I don't think it's deliberate, they just added the code they needed and didn't bother to test the rest. I can't blame them for that, but it is damn confusing to have the script doing such weird things at points.

It's an improvement, but the wasteland 2 download is still a single massive 10.3 GB file. I'm not quite sure why they couldn't segment it off into several smaller downloads, tar does support splitting.

I covered this for you ;)
https://www.gog.com/mix/playit_for_debian_gamers_and_their_ubuntu_friends

I’m working right now to support the new MojoSetup installers. Hopefully I’ll have some new scripts to push online tomorrow.
Once it’s done, I fully encourage every hacker here to study them and send me new scripts for games I don’t support yet, I’ll add them on my server and to the GOGMix with due credit ;)

Thanks.

I generally prefer to do things manually, than running scripts.
I'm glad that GOG is taking Linux seriously though.

Nice, thanks for your effort!