Conversation
`libpurple-lurch` is more popular than `libpurple-lurch-git` and will only track tagged releases, which is what most people probably want. To avoid long lines the URLs have been hidden behind Markdown links.
| ##### 2B. OR: Install from a community repo | ||
| * Arch - AUR: https://aur.archlinux.org/packages/libpurple-lurch-git/ | ||
| * Fedora - COPR: https://copr.fedorainfracloud.org/coprs/treba/pidgin-lurch/ | ||
| * Arch - AUR: [libpurple-lurch](https://aur.archlinux.org/packages/libpurple-lurch/) or [libpurple-lurch-git](https://aur.archlinux.org/packages/libpurple-lurch-git/) |
There was a problem hiding this comment.
libpurple-lurch has been moved from AUR into core Arch so the first link has gone 404 by now. Could be fixed on the go or not. Also, there are potentially more repos/distros to list here (now or later), see https://repology.org/projects/?search=lurch
|
@deraffe are you interested in fixing the link? would the correct one just be https://aur.archlinux.org/packages/libpurple-lurch-git ? generally, that repology overview is pretty great. i think the most useful thing to do would be to ask repology to merge all the different project names into one (see https://github.com/repology/repology-rules) and then use an overview like https://repology.org/badge/vertical-allrepos/purple-lurch.svg?header=lurch or textual https://repology.org/project/purple-lurch/versions. out of scope for this pr, i'll seperate this to an issue later 🙂 |
3 participants
libpurple-lurchis more popular thanlibpurple-lurch-gitand willonly track tagged releases, which is what most people probably want.
To avoid long lines the URLs have been hidden behind Markdown links.