[gentoo-user] "eix" and predicate "{isbinary}"

[gentoo-user] "eix" and predicate "{isbinary}"

[Dr Rainer Woitok]

Greetings,

are there any "eix" gurus out there?

I want to check whether or not some installed package was installed from
a binary or an ebuild.   However, according to "man eix" predicate "{is-
binary}" "returns 1 or empty depending on whether there is a correspond-
ing *.tbz2, *gpkg.tar, or *.xpak file for the version".  This is not ex-
actly what I need,  because an existing binary package for the same ver-
sion does not guarantee  that the package was really installed from that
binary:  if the USE flags don't match,  the package will nevertheless be
installed from the ebuild.

So, is there a way to persuade "eix" to reveal this information?   Or is
there any other command I could use?

Any hints welcome :-)

Sincerely,
  Rainer

Re: [gentoo-user] "eix" and predicate "{isbinary}"

[Dale]

Dr Rainer Woitok wrote:
> Greetings,
>
> are there any "eix" gurus out there?
>
> I want to check whether or not some installed package was installed from
> a binary or an ebuild.   However, according to "man eix" predicate "{is-
> binary}" "returns 1 or empty depending on whether there is a correspond-
> ing *.tbz2, *gpkg.tar, or *.xpak file for the version".  This is not ex-
> actly what I need,  because an existing binary package for the same ver-
> sion does not guarantee  that the package was really installed from that
> binary:  if the USE flags don't match,  the package will nevertheless be
> installed from the ebuild.
>
> So, is there a way to persuade "eix" to reveal this information?   Or is
> there any other command I could use?
>
> Any hints welcome :-)
>
> Sincerely,
>   Rainer
>
>


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. 
You take that qtwebengine package that takes so long to compile as a
example. If it spits out a time of a few minutes, that was a binary.  If
it is a long time, close to a hour or more, then it compiled it.  That
should work for the larger packages anyway.  Unless you have a really
fast CPU.

Also, don't forget equery u <package name> will display USE flags for
what is installed and what will be changed, if anything is changed. 
There may be a way to change what it looks at too.  I never went deeper
than what is installed and what it will install next. 

I hope someone has a much better answer tho.  I'm not 100% sure of what
you looking for.  I think I got a idea but I could be missing
something.  I'm working on cutting up that tree again and my back just
threw up a white flag.  My brain is somewhat divided at the moment.  One
part is trying to type, the other is letting me know my back is plenty
angry.  :/   I'm beating that tree tho.  Only got a log about 15 feet
long left.  Two more cuts. 

Dale

:-)  :-) 

Re: [gentoo-user] "eix" and predicate "{isbinary}"

[Dr Rainer Woitok]

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

Re: [gentoo-user] "eix" and predicate "{isbinary}"

[William Kenworthy]

[-- 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 --]

Re: [gentoo-user] "eix" and predicate "{isbinary}"

[Dr Rainer Woitok]

Bill,

On Thu, 17 Oct 2024 21:37:30 +0800 you wrote:

> ...
> Can you parse "/var/log/emerge.log"? It includes if its merging a 
> binpkg and where from.

That's very similar to the solution I'm using.  And at the end of anoth-
er script which installs,  upgrades or  uninstalls packages  I'm writing
the build types retrieved for all installed packages to a file for later
reference,  thus avoiding the need  to separately retrieve this informa-
tion only for a few packages every time I need it.

Sincerely,
  Rainer