> The behaviour is like this since there is no way to make sure
> that a new version of e.g. a library will compile in the presence
> of an already installed old version. (The installed headers
> might be found instead of the not-yet-installed new ones, causing
> strange compilation errors).

Given the size of modern disks, it ought to be possible to build
packages within a chrooted environment.
That way you could safely build all the packages before installing
any of them.

	David

-- 
David Laight: david@l8s.co.uk