Added options for Arch Linux in the download options #1702
No reviewers
Labels
No labels
accessibility
app-parity
area: creator
area: daemon
area: design
area: devops
area: discovery
area: docs
area: installer
area: internal
area: livestream
area: performance
area: proposal
area: reposts
area: rewards
area: search
area: security
area: subscriptions
area: sync
area: ux
area: viewer
area: wallet
BEAMER
channel
comments
community PR
consider soon
core team
css
dependencies
electron
Epic
feature request
first-timers-only
good first issue
hacktoberfest
help wanted
hub-dependent
icebox
Invalid
level: 0
level: 1
level: 2
level: 3
level: 4
merge when green
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
notifications
odysee
on hold
playlists
priority: blocker
priority: high
priority: low
priority: medium
protocol dependent
recsys
redesign
regression
resilience
sdk dependent
Tom's Wishlist
trending
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-desktop#1702
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "master"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Added the AUR URLs to the default download options under "Alt. Linux Build"
Before - http://hfimg.pw/i/g4py9.png
After - http://hfimg.pw/i/ohzrm.png
How is the LBRY app being added to that site?
It is the AUR (Arch User Repository).
Currently, there is only .tar.gz and .deb versions of the LBRY Application for Linux. Users of Arch Linux can use the AUR to clone and build the application with a simple (packagebuild/PKGBUILD) script.
The script installs dependencies and the application for them. Think of it like make and make install, but far more simple.
What do we have to do to upload to that site?
There are instructions on the Wiki page.
https://wiki.archlinux.org/index.php/Arch_User_Repository#Submitting_packages
Create an AUR account, add your SSH key to your profile, and use some Git commands to commit and push to the AUR repositories.
Do you know if that process can be automated?
No, not really as the AUR is user-maintained and the maintainers/author of each repository have to manually commit and push the updates.
I, along side others on the AUR would gladly keep the
lbry-app-release
repository up to date as new LBRY application versions are released.Hi, I am the maintainer for the current AUR package and have been faithfully doing so for over a year. I received a merge request for your package,
lbry-app-release
, @kcseb .@seanyesmunt yes it can technically be automated if I were to listen for releases on LBRY then run a script to update the package. I haven't had time to look into this. As of right now however, I manually update and test the packages locally.
I will happily add anyone from LBRY as a maintainer on the AUR for managing releases too.
@seanyesmunt I'd support adding this along with the flatpak support in a community maintained section of the readme: https://flathub.org/apps/details/io.lbry.lbry-app
Was planning on bringing that up today. Yeah, I think it would be a great idea to have another table below the current downloads table titled "Community-maintained releases" With a note describing it.
We just need to figure out how we want to support the autoupdate process for them. Right now, they would get prompted to download the deb file. Maybe we can disable this for flatpaks/aurs.
Someone also mentioned making a ppa for the deb, and the update process would also be a bit less painful.
The longer-term autoupdate process would include either appimage or snaps, as this is what electron builder currently supports.
I'll get a new community maintained section created for Flatpak/AUR builds. I'd ask @TimurKiyivinski / @kcseb to look after the AUR package and @iuyte for the flatpak (also asked @choffee as he just submitted one for 0.22.2 - https://github.com/flathub/io.lbry.lbry-app/pull/9)
I'll open a separate issue for dealing with auto update and maybe a community member can look into it.
@TimurKiyivinski if you'd like to assign me as a co-maintainer on the AUR, my handle is the same as here on GitHub (kcseb) Thank you.
@TimurKiyivinski
We've updated to 0.23, Referring to your previous comment; "I will happily add anyone from LBRY as a maintainer on the AUR for managing releases too." It would be appreciated if you could add me as a maintainer on the AUR as I am active on the LBRY Discord and would have word first if the package needs updating.
Thank you.
@kcseb I've added you as a co-maintainer, but please do not attempt hijacking packages any more.