Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#67515 - [discord] suggestion about updating

Attached to Project: Community Packages
Opened by g_o (g_o) - Friday, 07 August 2020, 01:19 GMT
Last edited by Eli Schwartz (eschwartz) - Friday, 07 August 2020, 01:42 GMT
Task Type General Gripe
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

hey so i'm trying to figure out .. i asked the irc already, i just want input from the maintainer..
is there a solution to the delay it takes for it to get to the stable mirrors? im not trying to complain i just dont understand what's the use of sourcing the package from the stable repos if i have to choose between updating manually and waiting an indefinite amount of hours

my ideas for now:
- the best idea i have for now, although a bad practice is to make the package version "dynamic" so that one can reinstall and get the latest version instead the current version.
- use testing branch for this package (use 2 configs for pacman); i dont believe it's a good solution to require any discord user to set up multiple configs
- somehow work with the discord team to make their updater work

let me know what you think
This task depends upon

Closed by  Eli Schwartz (eschwartz)
Friday, 07 August 2020, 01:42 GMT
Reason for closing:  Not a bug
Additional comments about closing:  That's not how pacman works.

Loading...