From: flameeyes@gmail.com (Diego 'Flameeyes' Pettenò)
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Remember: workarounds don't warrant RESO FIXED!
Date: Sun, 16 Nov 2008 17:24:34 +0100 [thread overview]
Message-ID: <m2od0fy6yl.fsf@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
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/
[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]
next reply other threads:[~2008-11-16 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-16 16:24 Diego 'Flameeyes' Pettenò [this message]
2008-11-16 16:48 ` [gentoo-dev] Remember: workarounds don't warrant RESO FIXED! Serkan Kaba
2008-11-16 17:42 ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2008-11-16 21:33 ` Ryan Hill
2008-11-17 8:52 ` Peter Volkov
2008-11-19 9:08 ` Alec Warner
2008-11-19 22:58 ` Ryan Hill
2008-11-19 23:49 ` Diego E. 'Flameeyes' Pettenò
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2od0fy6yl.fsf@gmail.com \
--to=flameeyes@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox