For quite awhile I've been wondering about the last line of the ecm.eclass live ebuild bug warning (ecm.eclass in both ::gentoo and ::kde, tho the live ebuilds the warning talks about are in ::kde): """ einfo "Do _NOT_ file bugs at bugs.gentoo.org because of this ebuild!" """ That directly contradicts the overlay's bug-filing instructions found at: https://wiki.gentoo.org/wiki/KDE/Ebuild_repository#Reporting_bugs """ Please file bugs on Bugzilla, prepending the summary with [kde overlay]. Additionally, pull requests are accepted at the Github mirror. """ Actually, that really needs updated too as it doesn't mention choosing the "Overlays" component, presumably because it predates it... (With the eclass in both ::gentoo and ::kde but the warning really only applying to ebuilds in the overlay, I'm not sure on the bug classification and title/summary. Feel free to make it more appropriate.)
Message has been simply carried over from kde4-base.eclass, tracked its history back to 2009 right from the start of introducing it: https://github.com/gentoo/kde/commit/7748347a1a28ad4de714cd0daf1fcd599e68476c It might have been in kde.eclass (KDE 3 times) already but kde overlay history is failing me there. I'm of two minds about this message. On the one hand, considerate bug reports are very much appreciated, when they are packaging related. We don't want a bug report for every temporary upstream build failure, and we are just lucky to live in a stable development time where that does not happen a lot (might change with Qt6/KF6 migration). We also don't want to have upstream be spammed with bugs caused by downstream packaging lagging behind. On the other hand, how many people will be reading this message anyway...
Maybe someone could express these sentiments in few words in a replacement message?
