| 1 |
On 2023-02-18 10:45-0500 Steven Lembark <lembark@×××××××.com> wrote: |
| 2 |
|
| 3 |
> First time I've ever seen a package install into PORTAGE_TMPDIR... |
| 4 |
> |
| 5 |
> Q: What am I missing? |
| 6 |
> |
| 7 |
> The rest of last nights "emerge --update" went into places like |
| 8 |
> /usr/bin... where you'd expect. After the upgrade I noticed that |
| 9 |
> virt-manager wasn't there. Tried emerging it alone to see what |
| 10 |
> had happened. |
| 11 |
> |
| 12 |
> # emerge ... app-emulation/virt-manager; |
| 13 |
> <time passes> |
| 14 |
> |
| 15 |
> # which virt-manager; |
| 16 |
> which: no virt-manager in |
| 17 |
> (/opt/bin:/opt/sbin:/bin:/usr/bin:/sbin:/usr/sbin) |
| 18 |
> <seems odd> |
| 19 |
|
| 20 |
Do you have the gtk USE-flag on app-emulation/virt-manager? Does |
| 21 |
`qlist app-emulation/virt-manager` show installed files? |
| 22 |
|
| 23 |
[…] |
| 24 |
> >>> Completed installing app-emulation/virt-manager-4.0.0 into |
| 25 |
> >>> /tmp/portage/app-emulation/virt-manager-4.0.0/image |
| 26 |
> |
| 27 |
> * Final size of build directory: 22080 KiB (21.5 MiB) |
| 28 |
> * Final size of installed tree: 7420 KiB ( 7.2 MiB) |
| 29 |
|
| 30 |
That is normal. it is installed into ${PORTAGE_TMPDIR} and then merged |
| 31 |
into ${EROOT}/ to make it less likely that the filesystem is getting |
| 32 |
messed up. |
| 33 |
|
| 34 |
Kind regards, tastytea |
Archives