On Wednesday 19 January 2005 15:31, Xavier Neys wrote:
Alexander Mieland wrote:
I think no. But the two timestamps are not from gcc, but from my very last merges (mysql and imagemagick). Simply strip the "| cut" part from this command and you'll see it.
Maybe our respective mail clients are playing tricks on you. Here is what the grep finds in my /var/log/emerge.log, created 2 years ago and still growing: # grep -aE '^[0-9]+: >>> emerge.*sys-devel/gcc-[0-9]|^[0-9]+: ::: completed emerge.*sys-devel/gcc-[0-9].*' /var/log/emerge.log
1052910706: >>> emerge (7 of 7) sys-devel/gcc-3.2.2 to / 1052911031: ::: completed emerge (7 of 7) sys-devel/gcc-3.2.2 to / 1052912349: >>> emerge (8 of 8) sys-devel/gcc-3.2.2 to / 1052913572: ::: completed emerge (8 of 8) sys-devel/gcc-3.2.2 to / 1052940849: >>> emerge (5 of 5) sys-devel/gcc-3.2.2-r2 to / 1052941195: ::: completed emerge (5 of 5) sys-devel/gcc-3.2.2-r2 to / 1052943389: >>> emerge (7 of 7) sys-devel/gcc-3.2.2-r2 to / 1052944714: ::: completed emerge (7 of 7) sys-devel/gcc-3.2.2-r2 to / 1053010624: >>> emerge (1 of 1) sys-devel/gcc-3.2.2-r2 to / 1053011914: ::: completed emerge (1 of 1) sys-devel/gcc-3.2.2-r2 to / 1053013800: >>> emerge (1 of 1) sys-devel/gcc-3.2.2-r2 to / 1053015087: ::: completed emerge (1 of 1) sys-devel/gcc-3.2.2-r2 to / 1055061950: >>> emerge (1 of 1) sys-devel/gcc-3.2.3-r1 to / 1055064360: ::: completed emerge (1 of 1) sys-devel/gcc-3.2.3-r1 to / 1077785512: >>> emerge (2 of 2) sys-devel/gcc-3.3.3 to / 1077787479: ::: completed emerge (2 of 2) sys-devel/gcc-3.3.3 to / 1084065532: >>> emerge (1 of 77) sys-devel/gcc-3.3.3-r3 to / 1084066348: ::: completed emerge (1 of 77) sys-devel/gcc-3.3.3-r3 to / 1086003006: >>> emerge (1 of 1) sys-devel/gcc-3.3.3-r5 to / 1086003893: ::: completed emerge (1 of 1) sys-devel/gcc-3.3.3-r5 to / 1086870277: >>> emerge (1 of 1) sys-devel/gcc-3.3.3-r6 to / 1086871130: ::: completed emerge (1 of 1) sys-devel/gcc-3.3.3-r6 to / 1094033069: >>> emerge (1 of 2) sys-devel/gcc-3.3.4-r1 to / 1094033997: ::: completed emerge (1 of 2) sys-devel/gcc-3.3.4-r1 to /
Whatever but I will not add basc to my portage group.
You must not set basc into the portage group. You have to set your user into this group then.
Let me rephrase that. I will not add the user that runs basc to the portage group.
I think nobody who has never emerged anything would install basc.
That was not a theoretical comment.
And, btw. if the gcc stats are not in the emerge.log, basc warns about it and gives a huge description what to do or not to do then.
Seen it, ignored it. I will not emerge gcc on boxes that do not need to emerge it just to let basc compute a time difference. I simply set GU=0
then you have two options. - unmerging basc ...or - manually adjust your GU on the webpage.
This is really no problem.
I had not noticed you could adjust it on the web page. Anyway, as I said, I set GU=0 in basc.conf and that's it. Once set, it's not a problem indeed. It's annoying it complains about not having any gcc stats nor any GU value. It could be more forgiving on that.
-- / Xavier Neys \_ Gentoo Documentation Project / French & Internationalisation Lead \ http://www.gentoo.org/doc/en /\
signature.asc
Description: OpenPGP digital signature
