aptitude has its own replacement for pkgCacheFile that it uses to initialize itself. Arguably this is bad; on the other hand, it seems to be the only way to create a subclass of pkgDepCache during startup instead of creating a straight pkgDepCache.
Anyway, it looks like the code to read the policy pin directory was placed into pkgCacheFile. I guess this is now part of the "official" startup ritual for apt. I still don't see a good way to use pkgCacheFile, unless I'm willing to create a junk pkgDepCache and throw it away (very expensive). I can't even change to using a proxy for the real DepCache, because I need to subclass it in order to configure its behavior. :-( So, I guess I'll just update the cut&paste job. Yuck. Daniel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
