Arch Linux User Repository

I've made some changes to this packages, and hopefully this works for everyone. I've added a few optional dependencies which namcap raised and changed how we deal with installing the package.

@Kuchiriel AND @TrialInError

Assuming there are no big changes, you delete the old souces (downloaded file from tibia.com) and run makepkg -s, it will fail because although the file from tibia.com always has the same name, it extracts to a folder with a specific name (the tibia client's current version).

Unfortunately, tibia has some compatibility problems with Arch Linux (not sure about other distros) that require small patches to configuration files, the problem is that this PKGBUILD's .patch files include the exact path of the tarball as downloaded from tibia.com and extracted with no additional flags, meaning we have to extract the tarball manually or run makepkg -s and wait as it fail every time in order to see the new name of the extracted file and edit the .patch files manually to refer to that new path so the package builds properly.

Resolving this issue is trivial, you just mv $extracted_path $static_path the tarball and use $static_Path in the patch files, it would require no maintenance whatsoever except that you would still need to pacaur/yaourt/other_helper -S tibia when the game fails to launch or if you were makepkg -s like the current maintainer likes to do: You would need to cd tibia && rm *tar && makepkg -s.

The BIG PROBLEM here is that Tibia is a game, I want to play, I play. The current PKGBUILD punishes me by saying I either need to go through several steps in order to play or I give up playing entirely until the maintainer "fixes" the package.

I've been trying to tell this to TrialInError for a few times now but I'm certain that this time my point got across, next time Tibia updates and requires manual intervention I'll push tibia-latest.

@TrialInError what is the exact path? We can patch manually? @RaphaelCosta There no automatic way to make this PKGBUILD? Or, how can we change PKBUILD to do what it is suposed to do without waiting for the maintainer?

@karimi It's happening because we must wait several hours for TrialInError to update his package every time CIPSOFT releases a minor update. ;)

@Karimi: Happening because of new upstream release. Due to the hardcoded version number in patch files they will fail if the exact path cannot be resolved. The failing checksum is a similar indicator.

I'm trying to install this package, but no matter what i do, the checksums don't match. and when i tell makepkg to skip checksums, instead i get some arcane prompt that i have no idea what to do. Any tips? Below are the lines i get for the situations mentioned.

==> Making package: tibia 11.54.6216-1 (Wed Jan 17 21:15:33 -02 2018) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found tibia-11.54.6216.tar.gz -> Found tibia-agreement.php -> Found 01_openssl102.patch -> Found 02_freetype.patch ==> Validating source files with sha256sums... tibia-11.54.6216.tar.gz ... FAILED tibia-agreement.php ... Passed 01_openssl102.patch ... Passed 02_freetype.patch ... Passed ==> ERROR: One or more files did not pass the validity check!

==> WARNING: Skipping verification of source file checksums. ==> Extracting sources... -> Extracting tibia-11.54.6216.tar.gz with bsdtar ==> Starting prepare()... [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.54.6216/start-tibia.sh |+++ tibia-11.54.6216/start-tibia.sh

File to patch:

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