From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Arfrever Frehtes Taifersar Arahesis <Arfrever@gentoo.org>
Subject: Re: [gentoo-dev] Minor changes in python.eclass and distutils.eclass
Date: Mon, 5 Jul 2010 18:29:09 -0400 [thread overview]
Message-ID: <201007051829.10904.vapier@gentoo.org> (raw)
In-Reply-To: <201007052223.52113.Arfrever@gentoo.org>
[-- Attachment #1: Type: Text/Plain, Size: 1155 bytes --]
On Monday, July 05, 2010 16:23:50 Arfrever Frehtes Taifersar Arahesis wrote:
> 2010-07-05 21:18:57 Mark Loeser napisał(a):
> > Arfrever Frehtes Taifersar Arahesis said:
> > > 2010-07-05 20:00:11 Mark Loeser napisał(a):
> > > > Everyone else has already made valid points. I'm just picking this
> > > > one to reply to now. Please remove the colors you have added. If
> > > > you need a new function, say "eqawarn", we should have that added in
> > > > the next EAPI with a description of when and where to use it.
> > >
> > > In case of the colored message added in this patch, if
> > > einfo/elog/ewarn/eqawarn/eerror was used, then its output wouldn't be
> > > logged by Portage.
> >
> > I don't understand what you are trying to say.
>
> Portage doesn't log output of einfo/elog/ewarn/eqawarn/eerror called in
> global scope.
dont call it in global scope then. the more parsing you do in global scope
the worse you make performance for the tree. these things get executed during
dependency generation which means it gets spammed even when not emerging.
use pkg_setup or something similar like everyone else.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2010-07-05 22:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-05 15:23 [gentoo-dev] Minor changes in python.eclass and distutils.eclass Arfrever Frehtes Taifersar Arahesis
2010-07-05 16:13 ` Samuli Suominen
2010-07-05 16:17 ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 16:26 ` Samuli Suominen
2010-07-05 16:34 ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 16:36 ` Tomáš Chvátal
2010-07-05 17:01 ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 17:38 ` Harald van Dijk
2010-07-05 17:43 ` Harald van Dijk
2010-07-05 17:55 ` Pacho Ramos
2010-07-05 18:06 ` Petteri Räty
2010-07-05 16:37 ` Ciaran McCreesh
2010-07-05 17:02 ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 18:00 ` Mark Loeser
2010-07-05 18:29 ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 19:18 ` Mark Loeser
2010-07-05 20:23 ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 21:28 ` Samuli Suominen
2010-07-05 21:38 ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 21:49 ` Samuli Suominen
2010-07-05 22:07 ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 22:29 ` Mike Frysinger [this message]
2010-07-05 23:31 ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 23:37 ` Mike Frysinger
2010-07-14 22:36 ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 18:26 ` Petteri Räty
2010-07-05 19:59 ` Arfrever Frehtes Taifersar Arahesis
2010-07-05 20:18 ` Petteri Räty
2010-07-05 19:37 ` Alex Alexander
2010-07-05 22:50 ` Jorge Manuel B. S. Vicetto
2010-07-05 23:18 ` Jeroen Roovers
2010-07-06 6:33 ` Petteri Räty
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=201007051829.10904.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=Arfrever@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