Arch Linux User Repository

@Zsar Thanks for the report, I pushed a fix

Seems to have some minor issues still:
- did not u+x <repository root>/RimSort.sh
- did not cp/ln/mv RimSort.sh to /opt/rimsort/RimSort.sh, where RimSort.desktop expects it
- /usr/share/applications/RimSort.desktop has been created but at least gnome-shell does not want to recognise it.

... Ah. Fixing RimSort.desktop to Exec=/usr/bin/RimSort makes it show up.
Personally, I think it would be nice if RimSort.sh were executable to start with, but otherwise this is the only change that is strictly necessary.

Ah I just had to rebuild it to get the update, thank you!

@esoterica It should be made by makepkg. But why try to run uv manually when I updated it?

Sorry if this is a dumb question, but where exactly would src/RimSort be? I tried running uv run python -m app in ~/.cache/yay/rimsort-git and ~/.cache/yay/rimsort-git/RimSort but neither of those work. I don't seem to have an src directory anywhere. Thanks :p

You're right, it makes its own .venv. I made it install that, and it seems to work. Please report back if there's any issues with this switch and I'll do my best to fix them!

My understanding of uv is that it will setup the .venv automatically and correctly, as long as it is used to wrap the python calls.

At least that is what it is supposed to be good for, is it not?

@Zsar Problem right now is that RimSort is built against 6.10.0 but Arch has 6.10.1. You can check that in pyproject.toml. I mean I could try to make the script fix the qt version in the project... But the painful build would remain.

I considered running it from git directly some time, but that caused other issues which I can't remember. Was before the switch to uv though. AFAIK this only works since you have pyside6 installed globally.

I can try to switch in the coming days, do you think I should add all the python dependencies back or use a venv maybe? Right now it's nicely bundled and I don't know the best practices.

@esoterica: Perhaps useful in the meanwhile: You can start the application without building it by, in src/RimSort, executing uv run python -m app.

That seems to work regardless of Qt version and is not even any slower than the compiled version.

I do not understand why the upstream has such an involved build process for seemingly no gain but additional problems, truth be told.

@DarkShadow44: Maybe it would be simpler to not build the application at all but to put uv run python -m app into the .desktop file and call it a day?

You could also drop the patchelf dependency that way: It is only needed for Nuitka. Not invoking Nuitka means not needing patchelf.

Mmh. Sadly I do not think the AUR build is at fault:
- r2009.d049b86 built two days ago did work for me when I built it and is broken now.
- r2015.6548feb built just now is likewise broken.

Must be resolved upstream, I fear.