Package Details: gog-planescape-torment 1.0.0.6-3

Git Clone URL: https://aur.archlinux.org/gog-planescape-torment.git (read-only)
Package Base: gog-planescape-torment
Description: Sigil... A place with gates that lead anywhere in existence, provided you have the proper key.
Upstream URL: http://www.gog.com/game/planescape_torment
Licenses: custom
Groups: games
Submitter: fettouhi
Maintainer: carstene1ns
Last Packager: fettouhi
Votes: 2
Popularity: 0.000000
First Submitted: 2014-11-11 14:03
Last Updated: 2015-06-11 18:24

Latest Comments

1 2 Next › Last »

beaylott commented on 2016-01-11 20:16

The GOG wiki suggests $HOME/.gog/$name on this (3.5 year old) wiki page:

http://gogwiki.com/wiki/AUR

That could work. Would be great to get this PKGBUILD up and running again.

Anonymous comment on 2015-09-29 13:24

I am thinking about adopting the package, but I am unsure how the tackle the savegame situation, and I don't wanna fuck it up for anyone. Also I am surprised to hear from you that the game saved correctly. Maybe it was due to the old version? 2.0.0.7 wouldn't let me without freezing.

Anyway, there are 2 possible solutions for the savegames that have their own dis/advantages, any comments?

1. Saved games in gamedir, folder owned by users group, with group write access.
+ Multiple users may save their game (
- May not be a good practise (?)
- Backups of home will not include the savegames

2. Create a .planescape-torment folder in /home/$USER/ and symlink to gamedir
- Only installing user may save his game
+ Backups of /home will preserve savegames
+ Seperation of game data and savegames seems to be a more logical approach

fettouhi commented on 2015-09-29 06:16

Don't have time to update this so I am disowning it.

@idlemachine: Yes, I tested the game and the save functionality.

Anonymous comment on 2015-09-28 23:52

Has anyone actually ever tried to play this or was this game installed only and never run? The game will try to save in /opt/gog-planescape-torment/saves, but normal users have no permission. This results in freezing the game... yay!

I rewrote the PKGBUILD to fix this and accommodate for the latest GOG installer. Constructive criticism is _very_ welcome as this is my first PKGBUILD actually.

Some comments though:
1. A post-install function was included to create a directory inside the game dir that is owned by the users group to circumvent the freeze. I do not know if this is actually allowed or good practise at all. However, I know that it worked for me.
2. On a related note, a post-remove function was provided to delete temporary files. Saved games are spared and can be manually deleted.
3. There's a small startup script (installed to /usr/bin). GOG's was discarded since it required another GOG helper script.
4. Also included is a new desktop entry, because newer versions don't come with one, but instead generate one on-the-fly with xdg-utils.
5. Included (lib32-)alsa-plugins as dependency for sound.
6. I made the .ini point to Z:/opt/gog-[...] since Z: is linked to root by default in wine.
7. The multi-language support was unfortunately ignored by me. International users are advised to ignore the checksums (--skipchecksums) and hope for the best.

I think that is all... See for yourself. Snapshot available on Google Drive:
https://drive.google.com/file/d/0B7TbrQ9dholhSUg2ckE5a1RQeGM/view?usp=sharing

Anonymous comment on 2015-09-28 23:38

Has anyone actually ever tried to play this or was this game installed only and never run? The game will try to save in /opt/gog-planescape-torment/saves, but normal users have no permission. This results in freezing the game... yay!

I rewrote the PKGBUILD to fix this and accommodate for the latest GOG installer. Constructive criticism is _very_ welcome as this is my first PKGBUILD actually.

Some comments though:
1. A post-install function was included to create a directory inside the game dir that is owned by the users group to circumvent the freeze. I do not know if this is actually allowed or good practise at all. However, I know that it worked for me.
2. On a related note, a post-remove function was provided to delete temporary files. Saved games are spared and can be manually deleted.
3. There's a small startup script (installed to /usr/bin). GOG's was discarded since it required another GOG helper script.
4. Also included is a new desktop entry, because newer versions don't come with one, but instead generate one on-the-fly with xdg-utils.
5. Included (lib32-)alsa-plugins as dependency for sound.
6. I made the .ini point to Z:/opt/gog-[...] since Z: is linked to root by default in wine.
7. The multi-language support was unfortunately ignored by me. International users are advised to ignore the checksums (--skipchecksums) and hope for the best.

I think that is all... See for yourself. Snapshot available on Google Drive:
https://drive.google.com/file/d/0B7TbrQ9dholhVF9QcnpiaXdaZlU/view?usp=sharing

@fettouhi:
You can of course use my edited script which is heavily based on the already existing one anyway. Sharing is caring!

Anonymous comment on 2015-09-28 22:50

Has anyone actually ever tried to play this or was this game installed only and never run? The game will try to save in /opt/gog-planescape-torment/saves, but normal users have no permission. This results in freezing the game... yay!

I rewrote the PKGBUILD to fix this and accommodate for the latest GOG installer. Constructive criticism is _very_ welcome as this is my first PKGBUILD actually.

Some comments though:
1. A post-install function was included to create a directory inside the game dir that is owned by the users group to circumvent the freeze. I do not know if this is actually allowed or good practise at all. However, I know that it worked for me.
2. On a related note, a post-remove function was provided to delete temporary files. Saved games are spared and can be manually deleted.
3. There's a small startup script (installed to /usr/bin). GOG's was discarded since it required another GOG helper script.
4. Also included is a new desktop entry, because newer versions don't come with one, but instead generate one on-the-fly with xdg-utils.
5. Included (lib32-)alsa-plugins as dependency for sound.
6. I made the .ini point to Z:/opt/gog-[...] since Z: is linked to root by default in wine.
7. The multi-language support was unfortunately ignored by me. International users are advised to ignore the checksums (--skipchecksums) and hope for the best.

I think that is all... See for yourself. Snapshot available on Google Drive:
https://drive.google.com/file/d/0B7TbrQ9dholha0JuSUpkNW9CcFE/view?usp=sharing

@fettouhi:
You can of course use my edited script which is heavily based on the already existing one anyway. Sharing is caring!

Anonymous comment on 2015-09-28 22:46

Has anyone actually ever tried to play this or was this game installed only and never run? The game will try to save in /opt/gog-planescape-torment/saves, but normal users have no permission. This results in freezing the game... yay!

I rewrote the PKGBUILD to fix this and accommodate for the latest GOG installer. Constructive criticism is _very_ welcome as this is my first PKGBUILD actually.

Some comments though:
1. A post-install function was included to create a directory inside the game dir that is owned by the users group to circumvent the freeze. I do not know if this is actually allowed or good practise at all. However, I know that it worked for me.
2. On a related note, a post-remove function was provided to delete temporary files. Saved games are spared and can be manually deleted.
3. There's a small startup script (installed to /usr/bin). GOG's was discarded since it required another GOG helper script.
4. Also included is a new desktop entry, because newer versions don't come with one, but instead generate one on-the-fly with xdg-utils.
5. Included (lib32-)alsa-plugins as dependency for sound.
6. I made the .ini point to Z:/opt/gog-[...] since Z: is linked to root by default in wine.

I think that is all... See for yourself. Snapshot available on Google Drive:
https://drive.google.com/file/d/0B7TbrQ9dholha0JuSUpkNW9CcFE/view?usp=sharing

@fettouhi:
You can of course use my edited script which is heavily based on the already existing one anyway. Sharing is caring!

fettouhi commented on 2014-11-19 10:57

The problem with the sed is that for some reason the ${lang_pkg} isn't accepted when editing the Torment.ini. That was why it was hardcoded into the PKGBUILD. But yeah you are right adding the "-" to the variables would lower the changes that each user has to make for each language and english would be included.

onkeldom commented on 2014-11-19 07:46

Thank you. Since I really appreciate guys like you doing their part for "gaming on linux", I'd like to throw in some ideas too (and not only complain about stuff ;) ):

Why don't you include the "-" char into the variables within the PKGBUILD? This way you would only need to edit the variables (and sadly the source, cause it's an "_" char there), but leave all the other lines as is:

lang_pkg="-polish"

If you leave the variables blank, this would install the english version, and as you fill in other languages, this would do for all the other... The sed lines would look almost equal:

sed -i s/'CD1:=.\+'/'CD1:=C:\\planescape-torment${lang_pkg}\\data\\'/ "${pkgdir}"/opt/gog/planescape-torment${lang_pkg}/Torment.ini

Since I'm no expert with sed, I'm only throwing in some further ideas:

* Do a single lang variable.
* "sed" it to different needs like _lang for the source, -lang for the other sed calls and -Lang ('1st char uppercase') for the other uses. This way you would only need one variable.
* For the different sha256sums, you could use an if-statement and check for the matching lang variable.

fettouhi commented on 2014-11-18 13:25

UPDATE: Rolling back to the English only PKGBUILD for now. As onkeldom said this multilingual version was a bit to messy.