-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Arch Linux AUR maintainer #78
Comments
actually, there are three version of bisq in AUR:
|
Can you consolidate those? |
Each of these have their place in the AUR (it is the Arch linux way, kind of). The interested user can either have a quick install (without the need for compilation, borrowed from a binary release), a stable install (built from release tag) or a cutting edge install (built from master). What characteristics do you suggest for a consolidated package? |
Ah, ok. |
2018.11 report
|
2018.12 report
|
2019.01 report
lets see how things evolve. |
2019.02 report
nothing new on the Wayland front |
2019.03 report
|
2019.05 report
|
2019.06 report
|
2019.07 report
|
2019.09 report
|
2019.10 report
|
Cycle 12 report
|
Cycle 13 report
|
Cycle 14 report
|
Cycle 15 report
|
Cycle 17 report
|
Cycle 18 report
|
Cycle 19 report
|
Cycle 20 report
|
Cycle 21 report
|
Cycle 22 report
|
Cycle 23 report
|
Cycle 24 report
|
Cycle 25 reportnothing happened |
Cycle 26 report
|
Cycle 27 report
|
Cycle 28 report
|
Cycle 29 report
|
The Arch Linux distibution builds all applications from source code and use the AUR format for delivering build instructions.
See: https://aur.archlinux.org/packages/bisq/
Primary role owner: @freimair (is maintainer of that AUR repository)
The text was updated successfully, but these errors were encountered: