| 1 |
On Wed, 12 Jan 2022 16:25:29 -0000 (UTC), Grant Edwards wrote: |
| 2 |
|
| 3 |
> > If it was installed through portage, there would have been an ebuild |
| 4 |
> > for it, in /var/db/pkg. |
| 5 |
> |
| 6 |
> Yes, correct past tense. There was at some point in the past when |
| 7 |
> ipkg-utils was installed. |
| 8 |
> |
| 9 |
> > That's what portage was referencing when if made the dependency |
| 10 |
> > calculations. |
| 11 |
> |
| 12 |
> There was no ipkg ebuild. There had been in the past, but it was |
| 13 |
> removed during an emerge --sync a while back. Last rites on 1 Aug |
| 14 |
> 2020, removal 30 days later: |
| 15 |
> https://www.mail-archive.com/gentoo-dev@l.g.o/msg90135.html |
| 16 |
|
| 17 |
The ebuild would still have been on /var/db/pkg as long as it was |
| 18 |
installed. |
| 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 |
Yes, in /var/db/pkg. That contains all the ebuild and data for installed |
| 25 |
packages, independently of what is currently in the portage tree. |
| 26 |
|
| 27 |
|
| 28 |
-- |
| 29 |
Neil Bothwick |
| 30 |
|
| 31 |
I'm Pink, Therefore I'm Spam |
Archives