On Tuesday 18 January 2005 22:57, Marius Mauch wrote:
On Tue, 18 Jan 2005 21:35:22 +0000 Ciaran McCreesh <[EMAIL PROTECTED]> wrote:
cp /var/log/emerge* /etc/basc
is really not a good idea. It's an even worse idea to do this on an ebuild that's being committed into the tree straight as stable, without going even a single minute in ~arch first.
well, do you have a solution for this?
See, basc, the client of gentoo-stats.org, needs read-access on /var/log/emerge.log to get the average mergetime of gcc. But unfortunately, the /var/log/emerge.log only has read-access for root and group portage. Others don't have any rights on it.
Okay, so how to do this then?
Regardless of security issues, IMvHO, it is not very clean to copy a bunch of log files into /etc. Couldn't the basc ebuild grep /var/log/emerge and dump its result into ${D}/etc/basc/whatever ? Just a sample grep that displays the timestamps of the latest gcc ebuild: # grep -aE '^[0-9]+: >>> emerge.*sys-devel/gcc-[0-9]|^[0-9]+: ::: completed emerge.*sys-devel/gcc-[0-9].*' /var/log/emerge.log|tail -n 2|cut -d':' -f1 1094033069 1094033997
Besides, relying on /var/emerge/log is not a good idea anyway. You can't be sure any gcc ebuild stats will still be in it.
Moreover, it is quite annoying to install your client on boxes that do not have any /var/log/emerge.log because they have never run emerge even though they have never run anything else but Gentoo in their whole life.
Hope this helps, -- / Xavier Neys \_ Gentoo Documentation Project / French & Internationalisation Lead \ http://www.gentoo.org/doc/en /\
signature.asc
Description: OpenPGP digital signature
