From: William Kenworthy <bill@kenworthy.id.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] "eix" and predicate "{isbinary}"
Date: Thu, 17 Oct 2024 21:37:30 +0800 [thread overview]
Message-ID: <ef8c455a-ed98-4e16-87c2-6c6885983fe4@kenworthy.id.au> (raw)
In-Reply-To: <67111156.df0a0220.2e3e7.8822@mx.google.com>
[-- Attachment #1: Type: text/plain, Size: 1290 bytes --]
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
>
[-- Attachment #2: Type: text/html, Size: 2461 bytes --]
next prev parent reply other threads:[~2024-10-17 13:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-13 18:21 [gentoo-user] "eix" and predicate "{isbinary}" Dr Rainer Woitok
2024-10-13 19:07 ` Dale
2024-10-17 13:29 ` Dr Rainer Woitok
2024-10-17 13:37 ` William Kenworthy [this message]
2024-10-17 15:00 ` Dr Rainer Woitok
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ef8c455a-ed98-4e16-87c2-6c6885983fe4@kenworthy.id.au \
--to=bill@kenworthy.id.au \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox