Log of emerge readable output produced somewhere?

[jeffk]

Is there a log being generated of my emerges' readable output that I can archive for later learning? I switched everything to gentoo recently and have a lot to learn about the system as I configure it.

I'm up to my ears in ebuilds of all the familiar packages I used under Redhat. I saw something flash by about having the gif use flag set, so libungif would assume I had libgif emerged and use that.

I'd like to have a searcheable archive of those kinds of messages. The compiler command output, not so much. Hopefully I'm not too late to start this archive if it was being generated all along. Any tips would be appreciated. Thanks.

Mod edit: Made this thread sticky instead of this merged one. --kallamej

[Earthwings]

there is /var/log/emerge.log, but it's fairly basic.

there are patches in bugzilla (Mod edit: bug 11359 --kallamej) to have the einfo and co. logged (that are the green messages you probably are interested in), but afaik it has not been integrated into portage yet. saving all the compiler output is as useless as space consuming, so piping in a file is no real option.

[soulwarrior]

Is there a log being generated of my emerges' readable output that I can archive for later learning? I switched everything to gentoo recently and have a lot to learn about the system as I configure it.

You must activate the logging-feature of emerge by setting the portage log directory in /etc/make.conf:

Code: Select all

# PORT_LOGDIR is the location where portage will store all the logs it
#     creates from each individual merge. They are stored as YYMMDD-$PF.log
#     in the directory specified. This is disabled until you enable it by
#     providing a directory. Permissions will be modified as needed IF the
#     directory exists, otherwise logging will be disabled.
PORT_LOGDIR=/var/log/portage

I'd like to have a searcheable archive of those kinds of messages. The compiler command output, not so much. Hopefully I'm not too late to start this archive if it was being generated all along. Any tips would be appreciated. Thanks.

You can then parse the messages in /var/log/portage with the bash utility portlog-info.

(ps: make it executable with "chmod +x portlog-info" and start it with "./portlog-info". You can get a list of available options with "./portlog-info --help")

Here you can find a threat, which lists all the utilities available for portage.

[mallchin]

Several tools have arisen that allow one to log/read the messages spurted out by portage.

I have tried both enotice and portlog-info and find enotice to be the better of the two, however it seems to have broken with the latest version of portage (2.0.51.21). I am wondering what tools other people use and which they find the best?

Have you written one of your own that deserves to see some daylight?

Also if anyone has a fix to solve enoitce's sandbox errors please post


-curtis119, made sticky and changed title to be more descriptive.

[Genone]

I like the logging support in portage-2.1

[mallchin]

LOL, so logging made it into portage now?

/me is still running 2.0.x, what tool(s) does 2.1.x use?

[Genone]

LOL, so logging made it into portage now?

/me is still running 2.0.x, what tool(s) does 2.1.x use?

Like about 99.999% of all gentoo users. What do you mean with "what tools"?

[mallchin]

I meant what tools does 2.1.x have to read notices as replacements for enotice and portlog-info...

Did one of the two make it into portage or does it have a new tool to do this?

[Genone]

Several options for that:
a) get the messages via mail
b) log them via syslog
c) stored in a folder
d) run a custom command to process them
e) any other way people are going to write a module for

No tool required.

[mallchin]

Cool. Sounds like they have it covered.

Can't wait. Have to make do with portlog-info until then.

[swimmer]

Hi all,

I tried both PORT_LOGDIR and enotice and have to admit that I find enotice *extremely* useful ... and as already pointed out in another (duplicate) thread I wonder why enotice can't be implemented in portage since it is so simple & easy to do?

Regards
swimmer

[Tschew]

Enotice should be on the top of the list of features that must be integrated into portage.

[curtis119]

Duplicate of this thread:

http://forums.gentoo.org/viewtopic-t-333009.html

I am consolidating and that thread is the best of the bunch.

[curtis119]

I moved a ton of other threads that were duplicates of this one. I'm making this one sticky.

[kallamej]

Re-consolidating the einfo threads as portage-2.1 is not yet available and this one contains relevant links. Merged http://forums.gentoo.org/viewtopic-p-23 ... ml#2377951 here. Sorry for the interleaving of some of the posts.

[kcy29581]

enotice is amazing! I actually feel like the pc has power now. It can emerge stuff and tell me afterwards in plain english what I, the slave, must do! I also used portlog-info first to go through all the logs before I used enotice.

gentooexperimental has some great tools which would be a great asset to portage. I have just returned to Gentoo after 3 months of distro-hopping (mostly used Arch Linux) and I am here to stay. The logs and emerge info were always my biggest gripes with Gentoo and now they are sorted!

Thanks!

[jeffk]

I'm curious, is enotice not yet included in portage, gentoolkit or some other package? I'd like to try it, but have only found this reference: http://gentooexperimental.org/script/repo/show/14

Perhaps there should be an ebuild for it?

[Genone]

There won't be an ebuild for it (unless someone outside {tools,dev}-portage wants to deal with it and the potential issues it will create).

[rikell42]

this is kind of weird.

why would logging be so difficult to figure out and not availiable as an ebuild?

is there a howto somewere that I missed?

[Genone]

Oh, it's not difficult at all. The reason why I'm not going to make a package for enotice is because it's (ab)using an undocumented portage feature to override internal functions, also it won't work anymore with portage-2.1 and has a (very remote) possibility to break profiles. In short: I can't support it even if I wanted, nor could any other portage developer.

[rikell42]

aww ok that makes sense.

I guess I will wate till things get integrated into portage before I mess with logging.

[kcy29581]

I know this is going to sound like I should just wait, but I'm curious as to when portage-2.1 "might" be out with logging features? I've been away from Gentoo for a few months so I'm a bit rusty with news...

I can wait for it! Just curious

[mallchin]

enotice seems broken for latest the portage, I can see it being a cat-and-mouse game...

portlog-info uses portage's built in logging features, probably less likely tro break...

[kcy29581]

I can see why portlog-info is hard (or damn near impossible!) to break, as it does a simple thing: looks at portage's OWN logs and filters out certain key words/phrases.

However with enotice, how could it break portage or anything for that matter? I thought that it did a similar thing to portlog-info, but rather than looking at the logs, it looks at the direct output and juts makes easily-readable files. It can't actually delete anything right?

[Genone]

I can see why portlog-info is hard (or damn near impossible!) to break, as it does a simple thing: looks at portage's OWN logs and filters out certain key words/phrases.

However with enotice, how could it break portage or anything for that matter? I thought that it did a similar thing to portlog-info, but rather than looking at the logs, it looks at the direct output and juts makes easily-readable files. It can't actually delete anything right?

The point is that it's overriding internal functions (actually inherited from baselayout atm) and 2.1 a) doesn't allow that anymore and b) changes those functions for it's own logging. So it won't delete anything, but it won't work anymore and might cause some random problems.