1.) I like Pamac and opted to first enable flatpaks in there and see if I could use it to install oninoshare. But it couldn’t even find it using the search function. Even after I downloaded teh flatpakref file, it still couldn’t find it.
Do you have any idea why that could be? I just ofund it weird to use the command line since pamac has worked so well for me.
2.) If the repository version has an issue, why even include it in the official repositories? By the same token, shouldn’t the AUR version at least work?
It just has users like me go down a rabbit hole thinking somethign should work when it doesn’t.
I have no idea - I don’t use advanced functionality in Pamac
I don’t know.
The package in the repo is packaged by Arch and the package has been flagged out-of-date since late february - Arch Linux - onionshare 2.2-5 (any) - probably why the repo package doesn’t work - and most likely also why the AUR package doesn’t work.
It is often useful to look at the upstream documentation - checking what they recommend - and how they recommend installation.
The Arch package is outdated - the current upstream version is 2.3.2.
I tested the Arch PKGBUILD - changed the version and updated the checksums. It fails to build using the current source - revealing a new upstream file structure and new dependencies.
My guess is the upstream maintainer currently doesn’t have time to rework the script, has found Arch dependency issues, whatever or simply forgotten it.
Flatpak is a very good way of creating a unified runtime environment - maybe the upstream onionshare developer is preferring that distribution method - who knows.