Rex Dieter wrote: > Thoughts? I can only summarize what I already posted to https://bugzilla.redhat.com/show_bug.cgi?id=1227295 : I think the settings Fedora currently ships are the right thing to do. Debugging output should always be disabled by default (opt-in). A de-facto *nix standard is that there should be no terminal output on success. GUI applications in particular should never spam the terminal. And when not run in a terminal, they log to .xsession-errors, so the logging spam even fills up persistent (HDD/SSD) storage. I would even silence qWarning by default. What we could try is going back to building applications with flags like -D_NDEBUG -DQT_NO_DEBUG. That would have the advantage of affecting only the applications we package, but the drawback that it's a compile-time setting and thus it is impossible to opt in to debugging without recompiling. The current setup affects everything using the packaged Qt, but can be changed by the user. I also strongly disagree with upstream developers who want to ship their applications with default-enabled debugging to their users. For their own development purposes, they should edit their local qtlogging.ini. For their users, the same arguments as for Fedora-packaged applications hold. Kevin Kofler _______________________________________________ kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kde@xxxxxxxxxxxxxxxxxxxxxxx/message/7DX6LJKBSYZFFUELNTYPZKI2DUQXZWRU/
