Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 4634 - emerge tool (ish)
Summary: emerge tool (ish)
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Core (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: Portage team
Depends on:
Reported: 2002-07-06 21:51 UTC by Ronald
Modified: 2011-10-30 22:38 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Ronald 2002-07-06 21:51:09 UTC
I wrote the script referenced in the above url because I was running a long 
string of commands including date and time every time I emerged a program,and 
wanted a simpler way to log my installs.  So I whipped this up, it is by no 
means an advanced script, but it gets the job done, and maybe some developer 
can take a look at it, and make something out of it.  The gist of the script is 
that you envoke it by placing it somewhere in your path (or by ./lec anywhere) 
and you use it instead of the standard emerge script, it does create massive 
logfiles, but they are really excellent for debugging any compile errors that 
happen while you're asleep and X is compiling, or if you want to have a handy 
way of remembering how long it took program foo to compile.  I also use it as 
an easy way to quickly see what I've already installed, even though there are 
utilities to do that already, this is perhaps just another way to do so.  Any 
feedback on my script would be welcome, I've been using it for my entire 
install, fixing up various portions of it, and am quite pleased with its 
execution, and low (?) overhead.

On a side note, could someone out there perhaps include "top" on the 1.4 boot 
CD?  I really would have liked to have been able to run it while I was 

Another thing about my script, if a newbie uses it, it ensures that there will 
be evidence of what they did wrong when they come up asking for help, just ask 
them to send you their /logs/foobar.emerge file.

That's all for now, and I'll apologize in advance for my slow server,luckily 
the script is small, and shouldn't take any time at all.  If it for some reason 
doesn't work (some people can't resolve it) then try:
However my IP might (unlikely) change, so I'd suggest trying the domain first.
Comment 1 Ronald 2002-08-03 15:40:05 UTC
It has come to my attention that /logs is a poor implementation for storing the 
log files.  Is there a Gentoo specific place one could store logfiles?  This 
ought to be something universal to Gentoo, not in the /tmp dir (gets cleaned 
out too often).  I think perhaps /var/log/gentoo would be acceptible, or 
even /usr/log.  However, I wasn't aware changing the root of the fs was 
unacceptible, I know it isn't supposed to be cluttered, but a /log directory 
seems to me to be a logical extension of the OS.  If anyone could give me a 
suggestion as to where the logfiles for a Gentoo system's emerges could be 
stored I will make the necessary changes, also note that I have posted a 
message regarding my script in the forums here:

Thank-you again for considering my script, suggesting fixes for it, and 
reviewing my other suggested additions (i.e. top on the installer, and "time" 
in the base system).
Comment 2 SpanKY gentoo-dev 2002-08-03 23:26:15 UTC
i would say use /tmp since that is where portage dumps log files currently ...
also, unless i'm wrong, since the logs you make arent really needed to be kept 
around for a long time so /tmp is ok
Comment 3 Marius Mauch (RETIRED) gentoo-dev 2003-11-26 16:29:20 UTC
This bug is quite old and the tool doesn't seem to be updated. Also we now have PORT_LOGDIR to log stuff and try to implement new tools in python instead of bash, so I close this bug.