-
-
Notifications
You must be signed in to change notification settings - Fork 659
Description
Hi! In the packaging guide, it says about acceptable AppImages:
- Should be available under a constant URL that does not contain the version number. Alternatively, should be available on GitHub Releases or the openSUSE Build Service (you are free to suggest additional serices like these)
I'd like to suggest accepting AppImages from the download section of bitbucket-hosted git repos. bitbucket kindly offers this space to developers to upload artifacts they have created. I, for example, distribute my Windows, macOS and Linux installers/bundles from the lux project's download section. If you look at that page, it has several AppImages - both versioned releases and also one which has 'master' in it's name which is the most recent Appimage to be had. AppImages are easily recognized by their extension, so it should be enough to communicate the URL of the download page, and if only versioned releases are wanted, a regular expression can narrow it down to AppImages following the usual naming scheme.
With this addition, a 'Download' button could be added to the catalog listing. In my case, where I only passed a single URL (the 'master' one) there was no Download button in the catalog, and none of the other links actually referred to my work, which isn't really my idea of what a catalog should do for me.