From: | Donnie Berkholz <dberkholz@g.o> | ||
---|---|---|---|
To: | gentoo-dev@l.g.o | ||
Subject: | Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: flag-o-matic.eclass | ||
Date: | Mon, 18 Feb 2008 21:54:37 | ||
Message-Id: | 20080218215434.GD3914@comet.science.oregonstate.edu | ||
In Reply to: | Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: flag-o-matic.eclass by Ciaran McCreesh |
1 | On 21:37 Mon 18 Feb , Ciaran McCreesh wrote: |
2 | > On Mon, 18 Feb 2008 13:20:52 -0800 |
3 | > Donnie Berkholz <dberkholz@g.o> wrote: |
4 | > > This seems like something ewarn should do on its own. |
5 | > |
6 | > http://sources.gentoo.org/viewcvs.py/portage/main/trunk/bin/isolated-functions.sh?r1=9118&r2=9140 |
7 | |
8 | Alright, so portage has put this stuff to stderr since January 4. Then |
9 | why are we also adding workarounds to individual eclasses? |
10 | |
11 | > http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/flag-o-matic.eclass?rev=1.121&view=markup |
12 | |
13 | I'm not sure what I'm supposed to get out of this, besides seeing that a |
14 | lot of stuff is sent to stderr. |
15 | |
16 | > http://thread.gmane.org/gmane.linux.gentoo.user/194929 |
17 | |
18 | Right, I figured the reason was something along the lines of info going |
19 | to stdout when only flags should. |
20 | -- |
21 | gentoo-dev@l.g.o mailing list |
Subject | Author |
---|---|
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: flag-o-matic.eclass | Ciaran McCreesh <ciaran.mccreesh@×××××××××××××.uk> |