| 1 |
On Wed, Dec 30, 2009 at 4:07 AM, Volker Armin Hemmann |
| 2 |
<volkerarmin@××××××××××.com> wrote: |
| 3 |
> On Mittwoch 30 Dezember 2009, Jon Hardcastle wrote: |
| 4 |
>> Guys, |
| 5 |
>> |
| 6 |
>> I have just done an emerge -eva system and it has |
| 7 |
>> installed/reinstalled/upgraded ~102 packages. When it finished i noticed |
| 8 |
>> some of them had some helpful YOU MUST DO THIS steps and i am wondering do |
| 9 |
>> they all have those or does emerge cleverly put all the messages at the |
| 10 |
>> end where they can be seen and digested? |
| 11 |
>> |
| 12 |
> |
| 13 |
> emerge elogv |
| 14 |
> read /usr/share/portage/config/make.conf.example and learn how to set up elog. |
| 15 |
> no message is lost ever again. |
| 16 |
> |
| 17 |
> but if haven't done it already, you are out of luck. |
| 18 |
|
| 19 |
Not necessarily... at least on my netbook here (running ~x86), with a |
| 20 |
very minimal make.conf and not a single line in it regarding elog, I |
| 21 |
have |
| 22 |
|
| 23 |
/var/log/portage/elog/summary.log |
| 24 |
|
| 25 |
... which just so happens to have every important emerge generated |
| 26 |
message since 2009-10-09 (which I believe was my original start to |
| 27 |
this one's build.) |
| 28 |
|
| 29 |
So... I do believe it might be default behavior now to keep, at the |
| 30 |
least, a summary log of everything. |
| 31 |
|
| 32 |
-- |
| 33 |
Poison [BLX] |
| 34 |
Joshua M. Murphy |
Archives