FS#42827 - Flagging out-of-date package should require comments.
Attached to Project:
AUR web interface
Opened by Claire Farron (clfarron4) - Tuesday, 18 November 2014, 00:41 GMT
Last edited by Lukas Fleischer (lfleischer) - Saturday, 03 October 2015, 08:03 GMT
Opened by Claire Farron (clfarron4) - Tuesday, 18 November 2014, 00:41 GMT
Last edited by Lukas Fleischer (lfleischer) - Saturday, 03 October 2015, 08:03 GMT
|
Details
When reporting official packages out-of-date, one must fill
out a comment saying why the package is out-of-date.
This would be useful for packages in the AUR, as some packages are marked out-of-date when they are not (I'm aware of this happening to kernel packages, when someone gets over-zealous and forgets to check ALL the sources). |
This task depends upon
Closed by Lukas Fleischer (lfleischer)
Saturday, 03 October 2015, 08:03 GMT
Reason for closing: Implemented
Additional comments about closing: Implemented in 4.1.0.
Saturday, 03 October 2015, 08:03 GMT
Reason for closing: Implemented
Additional comments about closing: Implemented in 4.1.0.
That is very good idea - "one must fill out a comment saying why the package is out-of-date" - and maintainer know, what going now.
The thing is that we want a system that works without taking it too far.
It wouldn't surprise me if a tickbox system for ticking which components of a package are out-of-date has already been considered in the past, but something tells me that it could be pretty messy to implement and you'd still want a text box there, for things like new dependencies/version bump due to library version change or something...
It's a tough one.
If you want to trim down the useless descriptions, you could either do what ArchWiki does and show a Red notification[1], or warn that the description (maybe even your username) will be visible in the package page.
[1] = http://i.imgur.com/XM1seJ9.jpg
FS#44967.