Bug#513663: [general] need infrastructure to check related packages

[Raphael Geissert <geissert@debian.org>]

Niels Thykier wrote:

> Speaking of unpacking; as I understand it we once had an "unpack-level
> 2" which has now been removed in favour of collection.  I am considering
> to remove the "unpack-level 1" as well and move everything to collection
> as a part of this.

The frontend needs a couple of tweaks in order to do that. The rest should 
be straight-forward, I think (but I might be wrong, it's been some months 
since I last looked at that item of my ToDo list.)
The frontend basically assumes that the package directory is already when it 
starts calling the collection scripts, however, the directory is created at 
unpack level 1.

The same tweak would be needed if we want the unpack level 1 replacement 
collection script to take care of removing the directory. The Auto-Remove 
flag should of course not be specified. The collection script needs to be 
called with 'remove-<package type>'

Deciding what collection scripts need to depend on the unpack level 1 
replacement might be tricky, though. Basically they all depend on it.

Cheers,
-- 
Raphael Geissert - Debian Developer
www.debian.org - get.debian.net