[gentoo-user] Re: Problem understanding "eix"

[Martin Vaeth]

Dr Rainer Woitok <rainer.woitok@×××××.com> wrote:
> Martin,
>
> On Monday, 2020-04-20 18:21:00 -0000, you wrote:
>
>> ...
>> >    app-crypt/tpm2-tss	2.3.3	0 1
>> ...
>>             The second value depends on your ARCH;
>> Since {isunstable} fails, I suppose that your ARCH is not amd64.
>
>    $ eix --dump | grep DEFAULT_ARCH
>    DEFAULT_ARCH="amd64"
>    $
>
> So no, that's a wrong assumption.

DEFAULT_ARCH is normally not used, because it should be set in
the profile. Does
  eix --print ARCH
also show amd64?

> farther down just tersly notes  "This is analogous  to availableversions
> with the difference that only installed versions are printed".
>
> So it boils down to the question what precisely "analogous" means

It means that it refers to the installed versions (which have a
different set of data than the available versions).

>    $ cat acct-group/input-0/KEYWORDS app-crypt/tpm2-tss-2.3.3/KEYWORDS |
>      xargs -n1 | grep '^~?amd64$'
>    amd64
>    ~amd64
>    $
>
> So the information is clearly there.

Yes, but it has no meaning (except in *.tbz2 files).
Therefore eix ignores it. There are no plans to change this.

>    export FMT="<category>/<name>\t<version>\t{isstable}1{else}0{} "
>    FMT=$FMT"{isunstable}1{else}0{}\n"
>    eix --format '<availableversions:FMT>' \
>        --category-name --regex 'app-crypt/tpm2-tss$|acct-group/input'

[reformatted slighly to avoid length restriction]

>    app-crypt/tpm2-tss	2.2.3-r2	1 1
>    app-crypt/tpm2-tss	2.3.3	1 1

This is strange: Both versions are only ~amd64, and in your previous
posting the output for {isstable} was indeed 0. So there appears to be
a contradiction with your previous posting.
Also the output of {isunstable} is the opposite of your previous posting.
I re-checked, and the keywords have not changed in the gentoo
repository. Do you use a different repository or do you have modified
something?

> The manual mentions in another place that the  "test for
> markedversions always fails  in the context of <installedversions:...>",
> but aparently there are also other properties  than just "markedversion"
> that always fail in this context.

Yes.

> But why does "<availableversions:...>"  only return a correct result for
> installed  virtual package  "acct-group/input-0"  but incorrect  results
> (stable and unstable at the same time) for both, the not installed pack-
> age "app-crypt/tpm2-tss-2.2.3-r2"  and the installed package "app-crypt/
> tpm2-tss-2.3.3"?

I don't know why the script now breaks for you:
For me the above script works: On amd64, I get the output

acct-group/input        0       1 0
app-crypt/tpm2-tss      2.2.3-r2        0 1
app-crypt/tpm2-tss      2.3.3   0 1

and on x86, I get the output

acct-group/input        0       1 0
app-crypt/tpm2-tss      2.2.3-r2        0 0
app-crypt/tpm2-tss      2.3.3   0 0