$ ebuild parano-0.3.3.ebuild install $ cat /var/cache/edb/counter 7713 $ la /var/log/portage/7714-parano-0.3.3.log -rw-r--r-- 1 peper portage 9.5K Jun 10 15:57 /var/log/portage/7714-parano-0.3.3.log $ su # ebuild parano-0.3.3.ebuild qmerge # cat /var/cache/edb/counter 7714 # la /var/log/portage/7715-parano-0.3.3.log -rw-r--r-- 1 root portage 448 Jun 10 15:59 /var/log/portage/7715-parano-0.3.3.log # ebuild parano-0.3.3.ebuild unmerge # cat /var/cache/edb/counter 7714 # la /var/log/portage/7715-parano-0.3.3.log -rw-r--r-- 1 root portage 946 Jun 10 16:02 /var/log/portage/7715-parano-0.3.3.log # logout $ ebuild parano-0.3.3.ebuild install tee: /var/log/portage/7715-parano-0.3.3.log: Permission denied
Perhaps we should encode the creation time of PORTAGE_BUILDDIR into the log name, in addition to the counter. That will allow the same log to be used in separate ebuild invocations that use the same build dir.
It seems that it's not possible to get a constant timestamp from $PORTAGE_BUILDDIR itself, so maybe we should use a hidden file inside of it to identify the log file. Perhaps $PORTAGE_BUILDDIR/.logid is good? It could just be an empty file and we could use it's UTC timestamp to generate the log file name. For the name of the log file, we could borrow the format used by pym/elog_modules/mod_save.py: ${CATEGORY}:${PN}-${PVR}:%Y%m%d-%H%M%S.log
sounds good to me ;]
This is fixed in svn r3506.
This has been released in 2.1.1_pre1.
