Arch Linux User Repository

pacman's tool makepkg, which is the only supported tool for building packages from AUR, doesn't default to /tmp. Such behaviour is introduced by wrappers like pacaur or yaourt, but not pacman.

And as you're shaking your head about my working process in this case, I'm in the same position with yours. So not everyone's personal preference.

And again. Everyone can do with the PKGBUILD whatever they want (although such behaviour can be made more difficult if wrappers are used which download a snapshot everytime a package shall be built instead using a local PKGBUILD). This is only a recipe. If the update process is to slow (which it is sometimes), or bothering (like the issues you have with the current process), one can change the PKGBUILD to his liking. If someone thinks more people can benefit from it he is free to upload the PKGBUILD to the AUR. But by no means is the maintainer in a position such as the maintainer from the supported binary repos of Arch. No one needs to wait for him to update the PKGBUILD.

Whereas a downloaded package named xyz.tar.gz, which wasn't deleted before (by mistake or whatnot (like using SRCDIR)) will get used again

So it won't install the new version if you have an older version downloaded? Well, both pacman and yaourt default to /tmp and at any pace deleting the old source is still a much better situation than the current one.

But yeah, that's entirely personal preference.

Everyone's personal preference is: I wake up, I want to play Tibia, I receive an annoying message saying "Your client is too old", I run "yaourt -S tibia or pacaur -S tibia" and Tibia magically updates.

I could see it as a bother for people if they download everytime a snapshot instead of cloning this repo

No, it's a bother for people when they need to go through several complicated steps in the morning to get their game to update. By the time you update this package several hours might have passed.

@RaphaelCosta: And disregarding the fact that -svn and -git packages work differently. Even if the cloned sources aren't deleted, you won't run into the problem with building an old version, as git fetch and the svn equivalent got invoked. Whereas a downloaded package named xyz.tar.gz, which wasn't deleted before (by mistake or whatnot (like using SRCDIR)) will get used again. There is no check involved, which compares with the upstream source.

And besides that, everyone can do with the PKGBUILD whatever they want. So if you think the idea is worth following you're free to do that. I told my point of view. The work involved on my side is minimal. I could see it as a bother for people if they download everytime a snapshot instead of cloning this repo and using git for fetching and applying changes. But yeah, that's entirely personal preference.

tl;dr: Introduce such a package if you want to. I have my doubts and therefor wouldn't maintain such a package.

@RaphaelCosta: What reintroduces the problem, if someone forgets to delete the old program files, the package will recreated with it. You can personally do those changes. And in regard of editing files. Therefore exists the possebility to create shell scripts --> dl the file, check on version number, sed the necessary files, git add, commit and push

Or this could tibia-latest like the hundreds of other -git, -svn packages in the AUR that always point to the latest version, there is no reason why you need to update this package every time CIP releases a small patch, it's more work for you and a bother for all of us.

If you really want to keep updating this every time I guess I'll have to push the tibia-latest package myself.

Please make sure your user belongs to the user group games (and propably a relogin needed). And the files in /opt/tibia must belong to root:games. It worked with sudo because you changed temporary to the user root (and he gets the stuff going). With this points cleared we can go on pinpointing and solving issues

The need for sudo is because Tibia is being installed in /opt/Tibia with 775 permissions, package should be adjusted to 777 to run Tibia from normal user.

I have deleted the sums of the PKBUILD and now installation worked.

(I have tried again without deleting the sums and worked anyway, wtf?)

But later

Tibia could not save your configuration: I/O error on file /opt/Tibia/conf/clientoptions.json: No such file or directory terminate called after throwing an instance of 'std::runtime_error' what(): Failed to create folder. [1] 13102 abort (core dumped) tibia

However with sudo, it works, why???

Anyway after I ran with sudo I was able to run without it (why?)

Update: It wont work, it only logs in, but character are unable to move...

sudo chmod 777 /opt/Tibia/* reduced warning and errors messages about permissions, but I still can't move the character.

Solved by changing Graphics Engine from 'OpenGL' to 'Software'

(I have observed that, after I did the chmod minimap now has persistent data saved, this wasn't happening before)

I hope my issues help to improve this PKG

Thanks!

@TrialnError I haven't just confirmed the default options.

@luan: Sorry, cannot help you with that

@RaphaelCosta: What reintroduces the problem, if someone forgets to delete the old program files, the package will recreated with it. You can personally do those changes. And in regard of editing files. Therefore exists the possebility to create shell scripts --> dl the file, check on version number, sed the necessary files, git add, commit and push

@Kuchiriel: Did you skip checking of checksums?

[tibia] Generating desktop file... ok can't find file to patch at input line 3 Perhaps you used the wrong -p or --strip option? The text leading up to this was:

|--- tibia-11.52.6104/start-tibia.sh |+++ tibia-11.52.6104/start-tibia.sh

File to patch: