Arch Linux User Repository

@Zsar so that issue is solved? Or is there something I should change?

... Aha! The src folder is also not under version control, like the pkg folder, and in src/RimSort/RimSort/libs the same three .so files must have been deposited by some prior build.

After deleting both pkg and src, the next ./makepkg went through as it should.

So, yes, old files not cleaned up by

git restore .
git clean -df .
git pull
makepkg

@DarkShadow44: Mmh. Yes, pkg/rimsort-git/opt/rimsort/libs/ contains three files - not symlinks - for me:

$ ls -l pkg/rimsort-git/opt/rimsort/libs/
total 608
-rw-r--r-- 1 Zsar Zsar 381976 Jan  8 21:33 libsteam_api.so
-rw-r--r-- 1 Zsar Zsar 110464 Jan  8 21:33 SteamworksPy.so
-rw-r--r-- 1 Zsar Zsar 126424 Jan  8 21:33 SteamworksPy_x86_64.so

When I delete the folder pkg, then makepkg recreates it and the three files are there once again.

So the ln cannot succeed in this direction.

lovely!

@o0d4: Pushed an update

As todds is not in repo but is included in binary releases, maybe you could add todds(https://aur.archlinux.org/packages/todds) package as an optional dependency for texture optimization feature?

Rimsort expects todds to be present in /opt/rimsort/todds so it requires a symlink /opt/rimsort/todds/todds -> /usr/bin/todds

ln [OPTION]... [-T] TARGET LINK_NAME

ln -s SteamworksPy_x86_64.so "$pkgdir/opt/rimsort/libs/SteamworksPy.so"

That should work, and it does for me - it creates a SteamworksPy.so linked to SteamworksPy_x86_64.so in the folder /opt/rimsort/libs/. The SteamworksPy_x86_64.so in that folder comes from src/RimSort/libs/SteamworksPy_x86_64.so, so I don't know what you mean.

Could it be that you already have a SteamworksPy.so? Would be nice to know why, I don't have one.

Stupid question: Why link SteamworksPy.so to SteamworksPy_x86_64.so if you could link src/RimSort/libs/SteamworksPy_x86_64.so - same file name - instead?

That way you can omit one of the arguments and it's (more) probably the correct file to begin with?

Mmh. More small things. Pulled and rebuilt today:

[...]
==> Starting package()...
ln: failed to create symbolic link '/home/Zsar/aur/rimsort-git/pkg/rimsort-git/opt/rimsort/libs/SteamworksPy.so': File exists
==> ERROR: A failure occurred in package().
    Aborting...

Responsible line:

ln -s SteamworksPy_x86_64.so "$pkgdir/opt/rimsort/libs/SteamworksPy.so"

should be

ln -s "$pkgdir/opt/rimsort/libs/SteamworksPy.so" SteamworksPy_x86_64.so

... but, err... should that file not come from a package and that package be a dependency? It's from this project, is it not? - Ah, we do not seem to have a package for that yet.

The options override in the PKGBUILD should be lowercase. Having it in all caps tries to override the one defined in makepkg.conf which is prevented when defined. This breaks the build with the default makepkg.conf which enables strip. Using all lowercase "options" causes makepkg to properly apply the changed setting.