On 2010-11-03 13:00, Jonathan Nieder wrote: > Yes, for some sense of the word "bug". During an upgrade it can be > very helpful to learn why the packages being upgraded are there in the > first place.
Agreed. > I suppose the problem is that callers do not know how to deal with > triggers? Here's a very naïve sketch. Untested. I haven't read the > relevant code paths, so it might not even do anything. :) "Callers"? But anyway, yes, I was trying to avoid dealing with trigger states. But I agree that could be postponed to worker, not cache builder. I will think about it. -- Eugene V. Lyubimkin aka JackYF, JID: jackyf.devel(maildog)gmail.com C++/Perl developer, Debian Developer -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
