Guys, please remember that if you work something around, you should _not_ close the bug as RESO FIXED but keep the bug open so that the issue can be addressed and fixed _properly_. Otherwise we'll end up with ebuilds full of workarounds without even documentation on why the workaround is applied!
With workarounds I mean, as examples: - FEATURES=test failures; - broken parallel make that requires -j1; - flags filtering, included -Wl,--no-as-needed appending This is important because: a) we want test to work or get fixed upstream; b) we want users to get parallel build if they request parallel build; c) we want --as-needed to be used, not ignored. If the bug is open and comes out on searches and all the rest, then we have higher chances that someone might _fix_ it, without having to look to see if there actually is one... Thanks! -- Diego "Flameeyes" Pettenò http://blog.flameeyes.eu/
pgp9wm4rF3mnl.pgp
Description: PGP signature
