Why aint elog save enabled by default in the make config and when an emerge is finnished just automatically echo the saved contents to the user? Isn't this what most users want? To actually see the important warnings/info for each package without having to watch the compile. To me it seems as all the required code for doing this is in place allready. The additions to the emerge script shouldn't be that overwhelming, to my understanding.

edit: I'm writing this because I in my last emerge -uD world by pure luck managed to catch an einfo message from GTK telling me to rebuild certain packages because they would break else. Why in the name of $DEITY is so important information allowed to just scroll by in useless compile output? For the record this wouldn't have been the first time my gentoo system got b0rken by an -uD world, and yes I _ALLWAYS_ run etc-update after my updates, regardless of if I was told or not.

Why aint elog save enabled by default in the make config and when an emerge is finnished just automatically echo the saved contents to the user? Isn't this what most users want? To actually see the important warnings/info for each package without having to watch the compile. To me it seems as all the required code for doing this is in place allready. The additions to the emerge script shouldn't be that overwhelming, to my understanding.

Agreed.

Crono81 wrote:

I only want to see the * BLA BLA and * BLA BLA informations of an ebuild, having it installed or not. How to do that?

Having emerged linux-headers, I was fortunate to see a notice's recommending a rebuild of glibc appear on the screen. Checking elogv and kelogviewer, though, I see no mention at all of linux-headers, let alone its messages. These two programs both show all of the other contemporaneous emerges, just not linux-headers.

Several people seem to be looking for a way to keep /var/log/portdir clean.
Just wanted to point out that the tmpwatch serves this purpose well and is very simple to configure.

Code:

# emerge tmpwatch

It installs the 15 KB binary /usr/sbin/tmpwatch, and it creates a little bourne script in /etc/cron.daily. There is no configuration file.

Add this line to the variables section near the top. You could manually assign PORT_LOGDIR (or just type /var/log/portage directly in the rule), but this will query portage to dynamically determine the correct location of its log directory so the script will still function if you change the log location:

Code:

PORT_LOGDIR="$(portageq envvar PORT_LOGDIR)"

Then down below, add a rule something like this to clean the portage log directory (delete the files that have not been modified in >=168 hours):

Code:

${TMPWATCH} --mtime 168 $PORT_LOGDIR

Alternative: If you want, you can exclude your elog directory like so (instead of line above):

Code:

${TMPWATCH} --exclude $PORT_LOGDIR/elog --mtime 168 $PORT_LOGDIR

Option: If so, and you still want to clean elog but after a different time, you could then insert a second rule below the first to handle it:

Yeah, you'll be pleased to know it comes already configured to clean distfiles and the portage tempdir. I primarily use a monthly eclean for that, but have tmpwatch sweeping up any remaining cruft months later.

Yeah, you'll be pleased to know it comes already configured to clean distfiles and the portage tempdir. I primarily use a monthly eclean for that, but have tmpwatch sweeping up any remaining cruft months later.

Where would a user figure out they need to make an elog directory? I mean other than searching here? I happened to know that I could set the log directory to gain more information. And I did read the entry in make.conf.sample (or is it example?) that talks about needing to create the /var/log/portage directory for this to work. But I didn't see anything about needing to make an elog directory too. And without it I get a list of what compiled, but not the after ebuild instructions.

Thankfully I have a new target to search under for this info, but I want to echo the disbelief that I have to manually get the list of things that packages have told me I must do. Things that may totally hose my system if I don't do them before I reboot are lost unless I know the magic handshake(s). Not the best way to make a user friendly system.

Posted: Sat Mar 01, 2008 5:38 pm Post subject: Re: This is what I have found.

OneOfMany wrote:

Where would a user figure out they need to make an elog directory? I mean other than searching here?

Well, you can put the log where you're up to, of course. Knowing the FHS and the ideas behind it helps a lot and is basic preconditioned Unix knowledge._________________Please make sure that you have searched for an answer to a question after reading all the relevant docs.

From the doc in /usr/share/doc/elogv-0.7.6.6/README.xz # you might have a different extension than .xz or none at all

Code:

Elogv is a simple tool written in python that allow you to easy read
portage elog files. To launch it, type on a console:

$ elogv

Inside the program, you can use these keys:

- Down arrow -> Scroll the list of files down by 1 unit
- Up arrow -> opposite of Down arrow
- Pag Down -> Scroll the list down by 10 unit
- Pag Up -> opposite of Pag Down
- End -> Go to the last file of the list
- Home -> Go to the first file of the list
- t -> order the list of files by date, most recent on top
- a -> order the list of files alphabetically
- r -> reverse the list of files
- SpaceBar -> scroll the selected file
- h or F1 -> show the help screen, press Page Up/Down to scroll up and down,
h and F1 again to hide
- d -> removes log files, usage is similar to vim "d" command, here are
same examples:
da -> removes all files
de -> removes from selected item to the end of the list
ds -> remove from selected item to the start of the list
d1d or dd -> removes selected file only
d4d -> removes 4 files starting from selected one
- q -> quit

Note:

To use this software you need the portage elog system configured on your
/etc/portage/make.conf, this is a simply configuration: