Patrick, I have been annoyed by this "feature" for years but actually never checked whether there's a report on that. I'm subscribing to this because I would like to see a database-supported dpkg as well. I wonder why that still hasn't been put into practice after 9 years since this bug was reported. And yes, the arguments from the original poster still apply today despite the much faster machines we run Debian on. I played around with RPM-based distributions and since RPM uses a DB-system (Berkely i.e.), it outperforms dpkg in this regard even though APT itself could keep up easily.
As for now, you can workaround this definancy by putting your root-partition (including /var where dpkg's database resides) on a solid-state disk (SSD). This speeds up the loopkup dramatically and makes installing packages real fun. Still, dpkg should be heavily improved in this regard. Maybe it is the turn of the Ubuntu-developers as they have the manpower to make a leap forward here. Let's hope for the best, Adrian -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
