From: Lares Moreau <lares.moreau@gmail.com>
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 13:02:43 -0700 [thread overview]
Message-ID: <1135713763.7402.20.camel@localhost> (raw)
In-Reply-To: <43B198D9.3000900@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1639 bytes --]
On Tue, 2005-12-27 at 21:41 +0200, 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?
I see the point about not showing all the QA stuff to the 'regluar'
user. Maybe only show this info on screen with --verbose set. As for
the QA-warnings file, how does this differ from parsing the files in
PORTLOG_DIR?
Later Days,
-Lares
--
Lares Moreau <lares.moreau@gmail.com> | LRU: 400755 http://counter.li.org
lares/irc.freenode.net |
Gentoo x86 Arch Tester | ::0 Alberta, Canada
Public Key: 0D46BB6E @ subkeys.pgp.net | Encrypted Mail Preferred
Key fingerprint = 0CA3 E40D F897 7709 3628 C5D4 7D94 483E 0D46 BB6E
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-12-27 20:07 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
2005-12-27 20:02 ` Lares Moreau [this message]
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=1135713763.7402.20.camel@localhost \
--to=lares.moreau@gmail.com \
--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