On 17/10/24 21:29, Dr Rainer Woitok wrote:
Dale,
On Sun, 13 Oct 2024 14:07:03 -0500 you wrote:
...
If no one has a better idea. This might help in a lot of cases. Just
do a genlop -t <package name> and look at how long it took to complete.
Well, I was after a precise solution :-)
...
I'm not 100% sure of what
you looking for.
I have a script which retrieves all sorts of relevant properties of the
packages specified. And now, after I started installing packages with
considerable build times from the binhost, the properties "binary ver-
sion available" and "binary version installed" simply have become rele-
vant too.
Meanwhile I have found a solution, but it isn't very elegant :-/
Sincerely,
Rainer
Can you parse "/var/log/emerge.log"? It includes if its merging a
binpkg and where from.
1728632742: >>> emerge (151 of 170) sys-apps/iproute2-6.9.0 to /
1728632743: === (151 of 170) _*Merging Binary*_
(sys-apps/iproute2-6.9.0::*/var/cache/binpkgs*/sys-apps/iproute2-6.9.0.tbz2)
1728632754: >>> AUTOCLEAN: sys-apps/iproute2:0
1728632754: === Unmerging... (sys-apps/iproute2-6.8.0-r2)
1728632758: >>> unmerge success: sys-apps/iproute2-6.8.0-r2
BillK