Bummer! Flathub doesn’t want me to use Gnome 3.38, since it’s EOL :-(
Developer by day, gamer by night!
🖥️ Stack: #NodeJS #Flutter #Go
🐧Linux: Currently on #Fedora
🎮️ Games: #ApexLegends and #Chess
Fun fact: Built my own custom keyboard, which sometimes doesn’t work and hangs, but hey… it still adds to the charm, right 😂
Bummer! Flathub doesn’t want me to use Gnome 3.38, since it’s EOL :-(
Noice! I got a successfull build of a flatpak bundle (without webkit) using GitHub actions. the bundle can be downloaded and installed via flatpak install --user xxx.flatpak and it’s running.
Now I need to figure out, how to publish this to Flathub.
TBH I’m fairly new to this. Gnome 45 sandbox has webkit2-4.1, while my PC build uses webkit2-4.0. Now, Gnome 3.38 sandbox has webkit2-4.0, but it still doesn’t run, due to missing libs. And I don’t know how to put everything together, so it works without having to re-build everything.
I managed to get it somehow working, but it got rejected by Flathub, because they don’t want me to build webkit and use the network during build (which I need)
I’m working on resticity, a restic frontend.
Let’s move this discussion over to GitHub, where I at least get the notifications for new messages.
I just made a PKGBUILD and commited it to the repo. Would you mind having a quick look at it and see if it’s good enough?
Right now, I’m looking through the docs of the AUR on how to publish it.
The project is in an too early phase to debate over SystemD. Can you guys please hold back with these arguments until pmOS reaches at least 4% market share.
yes… since it’s way easier to distribute, anything, by anyone.
Speaking of which… I’m the official maintainer of all the crypto wallets out there… trust me, bro!