| Summary: | Improve "ebeep/epause not defined" message in eutils.eclass | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Dennis Schridde <dschridde+gentoobugs> |
| Component: | Eclasses | Assignee: | Gentoo Quality Assurance Team <qa> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | trivial | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | eutils.eclass.patch | ||
Created attachment 262021 [details, diff]
eutils.eclass.patch
Describe it more verbosely.
I wonder whether we should rather just DIE since if somebody bothers to update the ebuild to new eapi they should at least try to install it and die makes them to fix it right away...
How shall I fix the package? I.e. what to use instead? PMS Appendix E doesn't talk about anything related being changed in EAPI-3. Search for "beep" and "pause" yields no results. Drop ebeep/epause! It's unreliable that users watch the install process when it beeps or sleeps for some seconds. Other measures (like the logging or news system) should be used. (In reply to Torsten Veller (RETIRED) from comment #3) > Drop ebeep/epause! It's unreliable that users watch the install process when > it beeps or sleeps for some seconds. Other measures (like the logging or > news system) should be used. I've sent a patch to gentoo-dev that will drop ebeep and epause: https://archives.gentoo.org/gentoo-dev/message/9629d845a7dfac6e17e6b8babab14199 eutils.eclass no longer defines ebeep and epause, and no ebuilds are left that call these functions. Closing. |
eutils.eclass defines for EAPI=3,4: ebeep() { ewarn "QA Notice: ebeep is not defined in EAPI=${EAPI}, please file a bug at http://bugs.gentoo.org" } epause() { ewarn "QA Notice: epause is not defined in EAPI=${EAPI}, please file a bug at http://bugs.gentoo.org" } From this description I am wondering if I am wrong to use it in my ebuild, or whether this is a bug in eutils.eclass. I would wish for the message to be improved to tell who is at fault and, if the ebuild is wrong, how to fix it. Reproducible: Always