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!
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!
FS#49540 - Narcissistic and vague description madness
Attached to Project:
Arch Linux
Opened by Mattias Andrée (maandree) - Thursday, 02 June 2016, 10:24 GMT
Last edited by Allan McRae (Allan) - Thursday, 02 June 2016, 11:03 GMT
Opened by Mattias Andrée (maandree) - Thursday, 02 June 2016, 10:24 GMT
Last edited by Allan McRae (Allan) - Thursday, 02 June 2016, 11:03 GMT
|
DetailsPlease stop the insanity of narcissistic and vague description for packages.
Consider extra/purpose for example. Its description is too vague: “Framework for providing abstractions to get the developer's purposes fulfilled” The only thing this tells be is that it is a framework, so the description could just have been “Framework”, or slightly more descriptive, “A KDE framework”. I don't actually know want this framework does so I will not be suggesting another description, but there is no sense in using the upstream description if it this vague. |
This task depends upon
Closed by Allan McRae (Allan)
Thursday, 02 June 2016, 11:03 GMT
Reason for closing: None
Additional comments about closing: File bugs for individual packages
Thursday, 02 June 2016, 11:03 GMT
Reason for closing: None
Additional comments about closing: File bugs for individual packages