| 1 |
On 2022-01-12, Neil Bothwick <neil@××××××××××.uk> wrote: |
| 2 |
> On Wed, 12 Jan 2022 14:53:06 -0000 (UTC), Grant Edwards wrote: |
| 3 |
> |
| 4 |
>> Then it must have been ipkg-utils itself that required the older |
| 5 |
>> python_exec, but there was no ebuild present for it. |
| 6 |
> |
| 7 |
> If it was installed through portage, there would have been an ebuild |
| 8 |
> for it, in /var/db/pkg. |
| 9 |
|
| 10 |
Yes, correct past tense. There was at some point in the past when |
| 11 |
ipkg-utils was installed. |
| 12 |
|
| 13 |
> That's what portage was referencing when if made the dependency |
| 14 |
> calculations. |
| 15 |
|
| 16 |
There was no ipkg ebuild. There had been in the past, but it was |
| 17 |
removed during an emerge --sync a while back. Last rites on 1 Aug |
| 18 |
2020, removal 30 days later: https://www.mail-archive.com/gentoo-dev@l.g.o/msg90135.html |
| 19 |
|
| 20 |
My conclusion was that dependency info for currently installed |
| 21 |
packages is also stored somewhere else, since emerge still knew that |
| 22 |
python-2.7 was required for ipkg-utils. |
| 23 |
|
| 24 |
-- |
| 25 |
Grant |
Archives