public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Make FEATURES=test the default
Date: Sat, 5 Aug 2006 14:35:49 -0400	[thread overview]
Message-ID: <200608051435.49746.vapier@gentoo.org> (raw)
In-Reply-To: <20060805125746.5aae6cd7@c1358217.kevquinn.com>

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

On Saturday 05 August 2006 06:57, Kevin F. Quinn wrote:
> On Sat, 5 Aug 2006 11:49:53 +0200
> Danny van Dyk <kugelfang@gentoo.org> wrote:
> > Please re-read the list of packages that fail tests:
> >  * glibc
> >  * autoconf
> >  * gettext
> >  * tar
> > That makes _4_ system packages. Before I would consider making
> > FEATURES=test a default, I would add least want the system set to
> > actually merge with it.
>
> So you're happy to let users install these packages without them
> knowing the tests would fail?

before i added binutils-2.17, i ran `make check` on it for about 25 
targets ... of those, about 10 failed ...

i checked with upstream and others reproduced it ... i dont know about you, 
but i dont have the skills to go in and fix the failures for all of those 
architectures

while i like the idea of all packages being able to pass FEATURES=test, 
somethings it just aint gonna happen with Gentoo's available skill set
-mike

[-- Attachment #2: Type: application/pgp-signature, Size: 827 bytes --]

  parent reply	other threads:[~2006-08-05 18:38 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-05  0:11 [gentoo-dev] Make FEATURES=test the default Kevin F. Quinn
2006-08-05  0:18 ` Ciaran McCreesh
2006-08-05  0:18 ` Alec Warner
2006-08-05  9:05   ` Kevin F. Quinn
2006-08-06 11:23     ` Paul de Vrieze
2006-08-05  0:25 ` Joshua Jackson
2006-08-05  9:33   ` Kevin F. Quinn
2006-08-05 11:14     ` Sascha Geschwandtner
2006-08-05 11:58       ` Marius Mauch
2006-08-05 12:21         ` Sascha Geschwandtner
2006-08-05 12:36           ` Sascha Geschwandtner
2006-08-05 13:29         ` Stephen P. Becker
2006-08-05 15:23           ` Marius Mauch
2006-08-05 18:31           ` Mike Frysinger
2006-08-05 18:56             ` Stephen P. Becker
2006-08-05 19:34               ` Mike Frysinger
2006-08-05 20:07                 ` Stephen P. Becker
2006-08-05 20:13                   ` Mike Frysinger
2006-08-05 20:20                   ` Ned Ludd
2006-08-05 11:15     ` Matthias Schwarzott
2006-08-05 13:50     ` [gentoo-dev] " Duncan
2006-08-05 13:50     ` Duncan
2006-08-05  0:26 ` [gentoo-dev] " Jakub Moc
2006-08-05 16:07   ` Tim Yamin
2006-08-06 12:31     ` Paul de Vrieze
2006-08-05  0:39 ` Danny van Dyk
2006-08-05  9:19   ` Kevin F. Quinn
2006-08-05  9:49     ` Danny van Dyk
2006-08-05 10:57       ` Kevin F. Quinn
2006-08-05 13:21         ` Ned Ludd
2006-08-05 18:35         ` Mike Frysinger [this message]
2006-08-05 18:48           ` Harald van Dijk
2006-08-05 19:35             ` Mike Frysinger
2006-08-05 19:25           ` Kevin F. Quinn
2006-08-05 15:14 ` [gentoo-dev] " Sven Köhler
2006-08-05 15:31   ` Markus Rothe
2006-08-05 15:35   ` Kevin F. Quinn
2006-08-05 15:48     ` Ciaran McCreesh
2006-08-05 16:04       ` Alec Warner
2006-08-05 17:49         ` Harald van Dijk
2006-08-18 22:03 ` [gentoo-dev] " Hanno Böck
2006-08-19  0:00   ` [gentoo-dev] " Christian 'Opfer' Faulhammer

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=200608051435.49746.vapier@gentoo.org \
    --to=vapier@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