I suggest that the USE flag "trace" to the ncurses ebuild, this would allow developpers to build ncurses with the "trace" (man 3 trace) which can help debugging code. One could also consider that the existing "debug" USE could auto flip "--with-trace", however as it's not done by default I assume someone doesn't want that to happen, hence the suggestion to add a "trace" use flag (it would probably require adding a short desc like "enables trace in ncurses (see man 3 trace)" to the use.desc.local file as welll). I'm attaching an ebuild which adds the "trace" USE. (note: all KEYWORDS are ~ in this ebuild) I've put this file in my overlay and emerged it and compiled it with a project of mine with success (the trace output data as expected to the trace file). emerge command: $ ACCEPT_KEYWORDS="~amd64" USE="trace" sudo emerge -va ncurses $ # yes, I know KEYWORDS="~amd64" is BadPratcice(tm) :P (full USE="doc gpm trace unicode -bootstrap -build -debug -minimal -nocxx")
Created attachment 89300 [details] the ebuild
now in 5.5-r3, thanks for the suggestion !
