| 1 |
A better idea would be if portage wrote those messages to a file and we |
| 2 |
could view it when we wanted. ie. We could have a showEbuildMessages or some |
| 3 |
such program that showed all those messages and allowed you to ack each one. |
| 4 |
I think this would be pretty useful as normally when i am fixing things i |
| 5 |
dont have time to fix all of it in one shot... |
| 6 |
Balaji |
| 7 |
|
| 8 |
-----Original Message----- |
| 9 |
From: John Robinson [mailto:strider@××××××.net] |
| 10 |
Sent: Tuesday, June 10, 2003 11:05 AM |
| 11 |
To: gentoo-dev@g.o |
| 12 |
Subject: Re: [gentoo-dev] A nice idea to improve portage |
| 13 |
|
| 14 |
|
| 15 |
> I know i know. there are some text at the end of the emerge that |
| 16 |
> says what you should do. |
| 17 |
> |
| 18 |
> But when your doind multiple emerge's one after the other and you |
| 19 |
> leave gentoo todo its thing. You don't see the text. |
| 20 |
> |
| 21 |
> So if there was a nice README file that explain the 'extra' setting |
| 22 |
> needed on each dir in portage then it would make things a LOT easier |
| 23 |
> and would be very helpful. |
| 24 |
|
| 25 |
Honestly, I think I'd much prefer if portage just queued all of those |
| 26 |
messages and displayed them at the end of the emerge. If that |
| 27 |
information was in a README, you'd have to go, find, and read the README |
| 28 |
for every package and dependency that you install. That's a lot of work. |
| 29 |
Since portage is supposed to be non-interactive, it shouldn't assume |
| 30 |
that you're gonna stick around watching the terminal while it does its |
| 31 |
thing. ;) |
| 32 |
|
| 33 |
- John |
| 34 |
|
| 35 |
-- |
| 36 |
|
| 37 |
Love justice; desire mercy. |
| 38 |
|
| 39 |
|
| 40 |
-- |
| 41 |
gentoo-dev@g.o mailing list |
| 42 |
|
| 43 |
-- |
| 44 |
gentoo-dev@g.o mailing list |
Archives