On 2023-02-18 10:45-0500 Steven Lembark <[email protected]> wrote:
> First time I've ever seen a package install into PORTAGE_TMPDIR...
>
> Q: What am I missing?
>
> The rest of last nights "emerge --update" went into places like
> /usr/bin... where you'd expect. After the upgrade I noticed that
> virt-manager wasn't there. Tried emerging it alone to see what
> had happened.
>
> # emerge ... app-emulation/virt-manager;
> <time passes>
>
> # which virt-manager;
> which: no virt-manager in
> (/opt/bin:/opt/sbin:/bin:/usr/bin:/sbin:/usr/sbin)
> <seems odd>
Do you have the gtk USE-flag on app-emulation/virt-manager? Does
`qlist app-emulation/virt-manager` show installed files?
[…]
> >>> Completed installing app-emulation/virt-manager-4.0.0 into
> >>> /tmp/portage/app-emulation/virt-manager-4.0.0/image
>
> * Final size of build directory: 22080 KiB (21.5 MiB)
> * Final size of installed tree: 7420 KiB ( 7.2 MiB)
That is normal. it is installed into ${PORTAGE_TMPDIR} and then merged
into ${EROOT}/ to make it less likely that the filesystem is getting
messed up.
Kind regards, tastytea
