From: Kalin KOZHUHAROV <kalin@thinrope.net>
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: Wed, 28 Dec 2005 10:34:07 +0900 [thread overview]
Message-ID: <43B1EB8F.9000009@thinrope.net> (raw)
In-Reply-To: <1135714953.7402.32.camel@localhost>
Lares Moreau wrote:
> On Tue, 2005-12-27 at 22:10 +0200, Petteri Räty wrote:
>
>>>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?
>>>
>>
>>Stuff that goes to PORT_LOGDIR is also shown to the user.
>
>
> Could it be split? Have the QA stuff shown on screen only when --verbose
> is set, but have all the information written to PORT_LOGDIR no matter
> the flag.
That will be difficult to explain as a behaviour, not logical to me.
> In my experience most users don't use PORT_LOGDIR in the first place.
> People who want the information define PORT_LOGDIR and have the
> information. Why add files containing duplicate information?
ditto.
Imagine a world where every (Gentoo) user is a developer... dream... more!
You are right - impossible. However, by bitching about problems, there are some users that decide to
check WTF is this warning, in turn they urge devs to fix it (and that is the main point of QA,
right?), they report it with their bug reports and so on. In other words, the problem gets _NOTICED_
by everybody.
IMHO, leave it as it is now and don't bother. It is not that much of an output, compared to the
compile output anyway.
I'd prefer even having it red/bold/whatever for easy spotting. And for the future, what about
defining something like GENTOO_LEVEL="n00b|user|know_how|master|admin|dev|guru" in make.conf? And
act acording to this, but trying to move the user up a level or two most of the time.
Kalin.
/know_how ->master -->dev/
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-12-28 1:37 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
2005-12-27 20:10 ` Petteri Räty
2005-12-27 20:22 ` Lares Moreau
2005-12-28 1:34 ` Kalin KOZHUHAROV [this message]
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=43B1EB8F.9000009@thinrope.net \
--to=kalin@thinrope.net \
--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