On Wed, 12 Jan 2022 16:25:29 -0000 (UTC), Grant Edwards wrote: > > If it was installed through portage, there would have been an ebuild > > for it, in /var/db/pkg. > > Yes, correct past tense. There was at some point in the past when > ipkg-utils was installed. > > > That's what portage was referencing when if made the dependency > > calculations. > > There was no ipkg ebuild. There had been in the past, but it was > removed during an emerge --sync a while back. Last rites on 1 Aug > 2020, removal 30 days later: > https://www.mail-archive.com/[email protected]/msg90135.html
The ebuild would still have been on /var/db/pkg as long as it was installed. > My conclusion was that dependency info for currently installed > packages is also stored somewhere else, since emerge still knew that > python-2.7 was required for ipkg-utils. Yes, in /var/db/pkg. That contains all the ebuild and data for installed packages, independently of what is currently in the portage tree. -- Neil Bothwick I'm Pink, Therefore I'm Spam
pgp59EK8L40Wl.pgp
Description: OpenPGP digital signature
