On 2018-07-16 06:02, Kevin Kofler wrote:
Rex Dieter wrote:
I can only summarize what I already posted to
I think the settings Fedora currently ships are the right thing to do.
Debugging output should always be disabled by default (opt-in). A
*nix standard is that there should be no terminal output on success.
applications in particular should never spam the terminal. And when not
in a terminal, they log to .xsession-errors, so the logging spam even
up persistent (HDD/SSD) storage.
I would even silence qWarning by default.
What we could try is going back to building applications with flags
-D_NDEBUG -DQT_NO_DEBUG. That would have the advantage of affecting
applications we package, but the drawback that it's a compile-time
and thus it is impossible to opt in to debugging without recompiling.
current setup affects everything using the packaged Qt, but can be
by the user.
I also strongly disagree with upstream developers who want to ship
applications with default-enabled debugging to their users. For their
development purposes, they should edit their local qtlogging.ini. For
users, the same arguments as for Fedora-packaged applications hold.
Pretty much this.
Developers shipping debug binaries to 'customers' are a plague.
I have the same issue with our inhouse developers - who generate ~1.9Gb
of logs per week from their mostly idle web apps. To make it worse, none
of it is actually useful.
I feel this is in the same category.
? netwiz(a)crc.id.au ? http://www.crc.id.au
? +61 (3) 9001 6090 ? 0412 935 897