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] Putting qa warnings to a text file instead of showing them to the world
Date: Tue, 27 Dec 2005 14:58:58 -0500	[thread overview]
Message-ID: <200512271458.58351.vapier@gentoo.org> (raw)
In-Reply-To: <43B198D9.3000900@gentoo.org>

On Tuesday 27 December 2005 14:41, Petteri Räty wrote:
> > On Mon, Dec 26, 2005 at 12:54:04AM +0200, Petteri Räty wrote:
> >>Currently there are quite a few ebuilds in the tree that execute dodoc
> >>or dohtml for files that do not exist. I think it would be nice to have
> >>ebuilds die if this is the case. To not break current ebuilds this would
> >>only happen with FEATURES="stricter". This is what I currently do in my
> >>bashrc. Obviously when integreted to portage one can use helper
> >>functions like hasq which are not available in bashrc.
>
> Well some people opposed this idea so what do everyone think about
> making portage output stuff like this to a qa-warnings (or whatever)
> file that developers can use? This would have the added benefit that
> users would not normally see this stuff and report stuff so easily but
> developers would still have easy access to it. Portage could even output
> a header to this file saying not to file bug reports unless you know
> what you are doing?

if we start "hiding" the output like that then most people will ignore them
-mike

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-12-27 20:04 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-25 23:32 [gentoo-dev] making dodoc and dohtml die when they fail and stricter is on Petteri Räty
2005-12-26  0:13 ` Jason Stubbs
2005-12-26 11:01   ` Jakub Moc
2005-12-26 12:53     ` Petteri Räty
2005-12-26 12:58     ` Danny van Dyk
2005-12-26 13:28     ` Jason Stubbs
2005-12-26 13:53       ` Re[2]: " Jakub Moc
2005-12-26  1:26 ` Diego 'Flameeyes' Pettenò
2005-12-26  2:28   ` Chris White
2005-12-26 12:04     ` Diego 'Flameeyes' Pettenò
2005-12-26 12:44       ` Petteri Räty
2005-12-26 12:59       ` Simon Stelling
2005-12-26 14:14         ` Diego 'Flameeyes' Pettenò
2005-12-26 14:32           ` Dan Meltzer
2005-12-26 14:44             ` Dan Meltzer
2005-12-27 19:41 ` [gentoo-dev] Putting qa warnings to a text file instead of showing them to the world Petteri Räty
2005-12-27 19:58   ` Mike Frysinger [this message]
2005-12-27 20:02   ` Lares Moreau
2005-12-27 20:10     ` Petteri Räty
2005-12-27 20:22       ` Lares Moreau
2005-12-28  1:34         ` Kalin KOZHUHAROV
2005-12-28  1:53           ` Lares Moreau
2005-12-28  2:03             ` Kalin KOZHUHAROV
2005-12-28  3:21           ` Ryan Tandy

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=200512271458.58351.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