sys-apps/portage-2.0.54 I just noticed my emerge.log file was very large. It might be beneficial to include in the files/ directory a logrotate conf file so that emerge.log could be cleaned periodically (similar to the way scrollkeeper provides it). The attached is my method, although there may be a better way.
Created attachment 79095 [details] sample logrotate configuration file for pruning emerge.log could be put in files/ in portage if desired. Feel free to modify or discard without attribution.
That would just break tools that rely on emerge.log being untruncated (like genlop).
genlop is not a Gentoo-developed application. It's a tool some users may choose to use. You criticized me for making an ebuild (pyflac) that benefits one program (musicbox). Now, I suggest your rejection of this enhancement for ONE program is also unwarranted. I think you should let the portage devs decide. Reopening.
Sigh... just rotate it yourself if you care so much about space, instead of breaking tools that are distributed in portage tree for no reason. # du -h /var/log/emerge.log 3.2M /var/log/emerge.log Wow, that's indeed huge, and FYI - this server has been installed on May 26, 2004. :P # du -h /var/log/emerge.log 2.6M /var/log/emerge.log The above installed Mar 19, 2005 and heavily used for testing.
there are more tools relying on emerge.log than genlop. *** This bug has been marked as a duplicate of 52675 ***
