From: Mike Gardiner <obz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] FEATURES_maketest_question
Date: Tue, 30 Nov 2004 15:54:47 +0800 [thread overview]
Message-ID: <1101801287.8811.9.camel@localhost> (raw)
In-Reply-To: <610e3466041130071933f743a0@mail.gmail.com>
> Personally, I use it because it gives me extra checks that a package
> is working correctly before I merge into my system and potentially
> break things. Since I am mostly using non-x86 this becomes more
> likely.
So peace of mind is your motivation?
> Btw, if we (as users) run into a package that fails maketest, is opening
> a bug the right thing to do?
I can't speak for all packages, but for GNOME packages, we'll take
patches you can provide that fix "make test" errors, but we don't have
time to look into fixing the tests ourselves.
Unfortunately, "make test" isn't uniformly adhered to upstream, and in
my experience, the tests that are conducted with it are often outdated,
and/or unmaintained. In these cases, "make test" doesn't provide any
indication of the state of the software - if it's
runnable/testable/linkable/however the tests are conducted.
This said, I'm not aware of (any?) Gentoo policy/stance on this, if
anyone can fill me in on that, please do.
Mike Gardiner
(Obz)
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-11-30 16:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 18:44 [gentoo-dev] FEATURES_maketest_question Rumen Yotov
2004-11-29 20:49 ` Joseph Booker
2004-11-30 4:50 ` Rumen Yotov
2004-11-29 22:53 ` Mike Gardiner
2004-11-30 15:19 ` Chris L. Mason
2004-11-30 7:54 ` Mike Gardiner [this message]
2004-11-30 18:24 ` Rumen Yotov
2004-11-30 12:49 ` Paul de Vrieze
2004-11-30 18:25 ` Rumen Yotov
2004-11-30 22:03 ` Joseph Booker
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=1101801287.8811.9.camel@localhost \
--to=obz@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