Autoupdate support for AUR and Flatpak #1762

Open
opened 2018-07-12 07:10:24 +02:00 by tzarebczan · 3 comments
tzarebczan commented 2018-07-12 07:10:24 +02:00 (Migrated from github.com)

The Issue

We have community maintained builds for AUR and Flatpak(https://flathub.org/apps/details/io.lbry.lbry-app) packages. The current auto update process for Linux only supports Debs and will trigger a download and install even on AUR/Flatpak builds.

This issue to do handle update notifications for AUR and Flatpak installs. The updater could simply tell the user which command to run in order to update when one is available. It should probably look at the version numbers in the respective community maintained repos.

The LBRY team is looking for a community contributor to take on this effort if they feel strongly about supporting additional Linux install processes. It may also be a possibility to work auto update into electron-builder, which only currently supports snaps.

System Configuration

Anything Else

Screenshots

Acceptance Criteria

Definition of Done

  • Tested against acceptance criteria
  • Tested against the assumptions of the user story
  • The project builds without errors
  • Unit tests are written and passing
  • Tests on devices/browsers listed in the issue have passed
  • QA performed & issues resolved
  • Refactoring completed
  • Any configuration or build changes documented
  • Documentation updated
  • Peer Code Review performed
<!-- Thanks for reporting an issue to LBRY and helping us improve! To make it possible for us to help you, please fill out below information carefully. Before reporting any issues, please make sure that you're using the latest version. - App releases: https://github.com/lbryio/lbry-app/releases - Standalone daemon: https://github.com/lbryio/lbry/releases We are also available on live chat at https://chat.lbry.io --> ## The Issue We have community maintained builds for [AUR](https://aur.archlinux.org/packages/lbry-app-bin/) and Flatpak(https://flathub.org/apps/details/io.lbry.lbry-app) packages. The current auto update process for Linux only supports Debs and will trigger a download and install even on AUR/Flatpak builds. This issue to do handle update notifications for AUR and Flatpak installs. The updater could simply tell the user which command to run in order to update when one is available. It should probably look at the version numbers in the respective community maintained repos. The LBRY team is looking for a community contributor to take on this effort if they feel strongly about supporting additional Linux install processes. It may also be a possibility to work auto update into electron-builder, which only currently supports snaps. ## System Configuration <!-- For the app, this info is in the About section at the bottom of the Help page. You can include a screenshot instead of typing it out --> ## Anything Else <!-- Include anything else that does not fit into the above sections --> ## Screenshots <!-- If a screenshot would help explain the bug, please include one or two here --> ### Acceptance Criteria 1. 2. 3. ### Definition of Done - [ ] Tested against acceptance criteria - [ ] Tested against the assumptions of the user story - [ ] The project builds without errors - [ ] Unit tests are written and passing - [ ] Tests on devices/browsers listed in the issue have passed - [ ] QA performed & issues resolved - [ ] Refactoring completed - [ ] Any configuration or build changes documented - [ ] Documentation updated - [ ] Peer Code Review performed
kauffj commented 2018-07-12 17:02:21 +02:00 (Migrated from github.com)

@tzarebczan @alyssaoc do we need an epic related to this? At a minimum, the copy on the linux download partial for lbry.io and the lbry-desktop readme ought to be updated.

@tzarebczan @alyssaoc do we need an epic related to this? At a minimum, the copy on the linux download partial for lbry.io and the lbry-desktop readme ought to be updated.
tzarebczan commented 2018-07-12 18:06:53 +02:00 (Migrated from github.com)

The readme is updated. I think we should link to that readme section from the lbry.io linux download page, as opposed to the download links themselves.

The readme is updated. I think we should link to that readme section from the lbry.io linux download page, as opposed to the download links themselves.
kauffj commented 2018-07-12 21:33:34 +02:00 (Migrated from github.com)

@tzarebczan I support that choice.

@tzarebczan I support that choice.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: LBRYCommunity/lbry-desktop#1762
No description provided.