From: Maurice van der Pot <griffon26@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] The usefulness of test in FEATURES
Date: Sat, 30 Apr 2005 15:48:18 +0200 [thread overview]
Message-ID: <20050430134818.GO8632@kfk4ever.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
Hey people,
A lot of ebuilds still fail when "test" is in FEATURES.
It's understandable that fixing this is a low priority thing, but what
I would like to propose is to either fix the tests or disable them.
The latter would be the thing to do for devs who are currently closing
bugs about tests with WONTFIX or similar.
By keeping tests that fail enabled in one ebuild, perfectly good tests
of any other ebuild are rendered useless because it becomes almost
impossible to upgrade a system with "test" in FEATURES.
If fixing the tests is not WONTFIX but rather something way down on your
todo list, I would also recommend disabling the tests in the ebuild.
A bug report could be used to track these bugs, but at least it would
not bother so many people while it is still unsolved.
I'd like to know what you think of this.
Thanks,
Maurice.
--
Maurice van der Pot
Gentoo Linux Developer griffon26@gentoo.org http://www.gentoo.org
Creator of BiteMe! griffon26@kfk4ever.com http://www.kfk4ever.com
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-04-30 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 13:48 Maurice van der Pot [this message]
2005-04-30 15:30 ` [gentoo-dev] The usefulness of test in FEATURES Rumen Yotov
2005-04-30 15:48 ` Jason Stubbs
2005-04-30 16:32 ` Rumen Yotov
2005-04-30 17:32 ` Maurice van der Pot
2005-04-30 17:45 ` Jason Stubbs
2005-04-30 17:54 ` Jason Stubbs
2005-04-30 19:43 ` [gentoo-dev] " R Hill
2005-05-01 1:27 ` Georgi Georgiev
2005-05-01 7:27 ` R Hill
2005-05-01 8:59 ` Jason Stubbs
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=20050430134818.GO8632@kfk4ever.com \
--to=griffon26@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