Yeah, maybe I am a bit confused by the various parameters to dpkg, and maybe if I were a developer it'd make sense, and maybe I oughta be more rigorous. But here is another example of a straightforward installation tripping up; I am sure that this will be one of the major problems that will have to be dealt with in testing.
I deleted cpp.info.gz and some other files in /usr/info, because I need ever spare byte of disk space. So gcc never did install properly. It runs, but is marked as unconfigured in the dpkg database. I never did get over this, but left it since it hadn't really had an effect. Today, I want to install g77. G77 tripped twice. First the gcc package has a copy of a f2c.h header and g77 wanted to overwrite it. I don't know if this is ok, but I said --force-overwrite. Next, gcc isn't really configured, so g77 won't complete its install. These are minor problems, but they come up with almost every installation. All because, I assume, I needed some disk space so I had to delete some info files I didn't need. Alan Davis
