1 |
On Thu, 2004-10-07 at 00:41, Lindsay Haisley wrote: |
2 |
> Thus spake Chris Gianelloni on Wed, Oct 06, 2004 at 05:43:27PM CDT |
3 |
> > On Wed, 2004-10-06 at 18:17, Lindsay Haisley wrote: |
4 |
> > |
5 |
> > It is still being worked on... there are a few preliminary patches out |
6 |
> > there that do this, but nothing has gone official yet. There's always |
7 |
> > /var/log/emerge.log, though... ;] |
8 |
> |
9 |
> Well yes, but emerge.log just says what was done, it doesn't record all the |
10 |
> notes, warnings, special instructions, etc. which were put into the package |
11 |
> by the gentoo devs and output using ewarn and einfo. |
12 |
> |
13 |
> This is not rocket science. e.g., in /etc/init.d/functions.sh, add the |
14 |
> following to the definitions of einfo and ewarn: |
15 |
> |
16 |
> if [ "${RC_DOC_FD3}" = "yes" ]; then |
17 |
> echo -e " ${GOOD}*${NORMAL} ${*}" >&3 |
18 |
> fi |
19 |
> |
20 |
> Then run |
21 |
> |
22 |
> # export RC_DOC_FD3=yes |
23 |
> # emerge blah 3> /tmp/foo |
24 |
> # less /tmp/foo |
25 |
> |
26 |
> This could be spruced up a bit so that each ebuild declared itself to fd 3 |
27 |
> so as to identify each section of comments in the output, but this shouldn't |
28 |
> be difficult. One would have to remember to always redirect to fd 3 to |
29 |
> avoid "bad file descriptor messages", but with a little effort this could be |
30 |
> supressed, I'd guess. |
31 |
> |
32 |
> Actually, this is so obvious that I think I'll just do it :-) |
33 |
|
34 |
Honestly, this discussion should go to #gentoo-portage or to the |
35 |
portage-dev list, since they're the ones that could make this happen. |
36 |
|
37 |
-- |
38 |
Chris Gianelloni |
39 |
Release Engineering - Operational/QA Manager |
40 |
Games - Developer |
41 |
Gentoo Linux |
42 |
|
43 |
|
44 |
-- |
45 |
gentoo-desktop@g.o mailing list |