Dale wrote: > Howdy, > > I do my updates in a chroot. When it is done in the chroot, I copy the > packages over to my main OS and install with -k and it keeps my running > OS more stable. There is one problem tho. When I do that, the emerge > times for installing the packages with -k, which is a LOT faster, are > also recorded in the emerge.log file. When I use genlop -c to see how > much longer a compile is going to take, it makes the results of genlop > way off. A package that may take a hour to compile can install as a > binary in a couple minutes. Poor genlop gets confused. Did the emerge > take a couple minutes or a hour? > > Is there a way that I can stop emerge from logging the package installs > with -k? Some little known option? > > I also thought about copying the emerge.log file over from the chroot > after I complete the -k update on my main install. Not logging the -k > update would be the same result. Thing is, I forget to do it. It would > be nice if I could use a emerge option but does anyone see a problem > with this way? > > Dale > > :-) :-) > > P. S. Got my tractor back together and even bladed a driveway this > morning. It's doing a LOT better but I want to rebuild the other side > pretty soon. No leaks and no parts left over. >
The only way I've come up with to work around this, copy the emerge log file over after I do my emerge -k on my main OS, if I don't forget. I wish I could just tell emerge not to log emerge -k at all. Dale :-) :-)
