public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev]  Re: Remember: workarounds don't warrant RESO FIXED!
Date: Sun, 16 Nov 2008 15:33:18 -0600	[thread overview]
Message-ID: <20081116153318.2090b45f@halo.dirtyepic.sk.ca> (raw)
In-Reply-To: m2od0fy6yl.fsf@gmail.com

[-- Attachment #1: Type: text/plain, Size: 1913 bytes --]

On Sun, 16 Nov 2008 17:24:34 +0100
flameeyes@gmail.com (Diego 'Flameeyes' Pettenò) wrote:

> 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;
*                              *
*                              *
********************************

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

The next person who closes testsuite failures as invalid or upstream
gets to meet my frozen boot.  If a test fails, fix it.  If it fails
because of portage or Gentoo-specific reasons that can't be fixed then
RESTRICT it.

Everybody is crowing about making src_test enabled by default, yet I
still had 2 out of 3 build failures on my last tinderbox adventure
caused by known, reported, and unfixed testsuite problems.

> - 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!
> 



-- 
gcc-porting,                                      by design, by neglect
treecleaner,                              for a fact or just for effect
wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-11-16 21:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 16:24 [gentoo-dev] Remember: workarounds don't warrant RESO FIXED! Diego 'Flameeyes' Pettenò
2008-11-16 16:48 ` Serkan Kaba
2008-11-16 17:42   ` [gentoo-dev] " Diego 'Flameeyes' Pettenò
2008-11-16 21:33 ` Ryan Hill [this message]
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=20081116153318.2090b45f@halo.dirtyepic.sk.ca \
    --to=dirtyepic@gentoo.org \
    --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