> 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. :-(
I had rewritten pkgCacheFile for my needs recently, maybe it is now possible to subclass pkgCacheFile and replace the BuildDepCache method for your needs, too? Just ignore me if i am wrong, i just stumbled across Tim Retout blogpost about this bug and remembered #535512. I haven't even looked to deep at the code as i can't test a patch anyway (compiling aptitudes needs more or less hours to build and i have just a few minutes currently…). Best regards David Kalnischkies -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
