AppImage handling about logoslinuxinstaller HOT 8 CLOSED

I haven't read through the whole list, but GH user @mmtrt has several wine AppImages continuously released here. You might find something interesting or even useful in there.

from logoslinuxinstaller.

I haven't read through the whole list, but GH user @mmtrt has several wine AppImages continuously released here. You might find something interesting or even useful in there.

This is the repo we download our AppImages from. The problem is there is no history, so we have to grab them before they're gone

from logoslinuxinstaller.

One thing to note: AppImageLauncher (AIL), a popular piece of software that integrates AppImages with the host system, causes a conflict with the wine AppImage and renders the program broken. We need to detect if AIL is running, and if so, prompt to disable it. This further requires a system reboot (or perhaps just logging back in) to remove the conflicting changes.

Manjaro enables AIL by default, for instance. There was some code I wrote in the commit linked above that attempted to account for AIL before realizing that AIL itself broke the wine AppImage.

from logoslinuxinstaller.

We either need to figure out how to grab something like an RSS feed for our AppImage releases on GitHub (and extract the URL for the download) or we need to store a list of our AppImages in a file in our Python app containing the URLs for quick reference. I'd prefer the RSS route as it would automated, but the URLs would be easy enough to update.

from logoslinuxinstaller.

GitHub has a very useful API, so we should fairly easily be able to filter out what we need using something like:

>>> import requests
>>> url = 'https://api.github.com/repos/FaithLife-Community/LogosLinuxInstaller/releases'
>>> r = requests.get(url)
>>> print(r.json()[0].get('assets')[0].get('browser_download_url'))
https://github.com/FaithLife-Community/LogosLinuxInstaller/releases/download/v4.0.0-alpha.1/LogosLinuxInstaller

from logoslinuxinstaller.

by the way, that's also where we can see some other interesting stats:

>>> import requests
>>> url = 'https://api.github.com/repos/FaithLife-Community/LogosLinuxInstaller/releases'
>>> r = requests.get(url)
>>> print(r.json()[0].get('assets')[0].get('browser_download_url'))
https://github.com/FaithLife-Community/LogosLinuxInstaller/releases/download/v4.0.0-alpha.1/LogosLinuxInstaller
>>> print(r.json()[0].get('assets')[0].get('name'))
LogosLinuxInstaller
>>> print(r.json()[0].get('assets')[0].get('size'))
27695128
>>> print(r.json()[0].get('assets')[0].get('download_count'))
6

from logoslinuxinstaller.

Now that we can find the branch version, we just need to modify the appimage handling code to do so.

Would it still be beneficial to keep our repos separate and make use of the API as such?

I like being able to get stats on actual number of users. We could run the same for the Ferion11 repo since that will have much more historical data.

I will modify the checklist in the OP.

from logoslinuxinstaller.

There is a new community repo here:

https://github.com/FaithLife-Community/wine-appimages/releases

Updated the app to use this new repo: 1d7024a

We should use this repo when attempting to fix the get AppImages from GitHub TODO and the update-to-latest GitHub AppImage.

It would be neat if the GUI could present some kind of highlighting or exclamation mark to the user on such an update command, running the check for a new version in the background.

from logoslinuxinstaller.