1st unpacking, 2nd dependency checking

[Martin Schulze <joey@finlandia.Infodrom.North.DE>]

This might be an faq.

But occasionally I notices that dpkg first unpacks and installs
the files in a particular package and checks dependencies afterwards.

This means that wrong dependencies are discovered when it is
too late since the old version of the package is already
overwritten.

I'm sure there is a rationale for this, but what is it?

At least I would have expected that dpkg tests the dependency
of new packages and refuses to unpack them - unless one told
it to ignore dependencies.

Regards,

	Joey

-- 
There are lies, statistics and benchmarks.