From: Jeroen Roovers <jer@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: changing the developer profile: FEATURES="test" -> FEATURES="test-fail-continue"
Date: Fri, 4 Jun 2010 18:48:38 +0200 [thread overview]
Message-ID: <20100604184838.77e5e331@epia.jer-c2.orkz.net> (raw)
In-Reply-To: <4C0917B1.8080307@gentoo.org>
On Fri, 04 Jun 2010 17:11:45 +0200
"Paweł Hajdan, Jr." <phajdan.jr@gentoo.org> wrote:
> What do you think about doing the following change in
> /usr/portage/profiles/targets/developer/make.defaults:
[..]
> What do you think?
I've never felt any need or obligation to use a developer profile. I
don't think I ever saw any announcement to that effect either. What is
the use of a developer profile?[1]
Someone in the know, please sell it to me. :)
Regards,
jer
[1] I've seen developers complain more and more about failing test
suites. Maybe that's a related issue? Developers now use the
FEATURES set out in a developer profile and can then extract some
kind of validity claim from the fact that I obviously didn't do my QA?
That would explain a lot.
next prev parent reply other threads:[~2010-06-04 16:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-04 15:11 [gentoo-dev] RFC: changing the developer profile: FEATURES="test" -> FEATURES="test-fail-continue" "Paweł Hajdan, Jr."
2010-06-04 15:35 ` Jesus Rivero (Neurogeek)
2010-06-04 15:50 ` "Paweł Hajdan, Jr."
2010-06-04 16:48 ` Jeroen Roovers [this message]
2010-06-04 17:00 ` Jeroen Roovers
2010-06-06 3:46 ` [gentoo-dev] " Ryan Hill
2010-06-07 10:10 ` Thilo Bangert
2010-06-07 12:02 ` Jeroen Roovers
2010-06-07 14:05 ` Thilo Bangert
2010-06-12 3:59 ` Ryan Hill
2010-06-07 13:53 ` "Paweł Hajdan, Jr."
2010-06-09 17:08 ` [gentoo-dev] " "Paweł Hajdan, Jr."
2010-06-10 16:28 ` Brian Harring
2010-06-10 16:36 ` Samuli Suominen
2010-06-10 17:36 ` Brian Harring
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=20100604184838.77e5e331@epia.jer-c2.orkz.net \
--to=jer@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