[gentoo-dev] Remember: workarounds don't warrant RESO FIXED!

2008-11-16 Thread Diego 'Flameeyes' Pettenò

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


Re: [gentoo-dev] Remember: workarounds don't warrant RESO FIXED!

2008-11-16 Thread Serkan Kaba
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

I think, resolving as UPSTREAM might be more logical as we can't force
every upstream to fix their *borked* build system and the bug will be
left open forever.

Diego 'Flameeyes' Pettenò yazmış:
 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!
 

- --
Sincerely,
Serkan KABA
Gentoo/Java
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkkgTssACgkQRh6X64ivZaJq7gCfUSK2fcYQTXeddGfcM0xBLx2S
elQAn3S0hc62XuLrubvpn7kCQhwfiIim
=mvB8
-END PGP SIGNATURE-