Package: deborphan Version: 1.7.23 Severity: wishlist Here is an example of the problem I encounter on a regular basis:
package App depends on libB package libB depends on libC package libC depends on libD Say we remove App, then libB becomes an orphan and deborphan correctly returns it. However, once we remove libB, libC becomes an orphan (it wasn't before) and then libD becomes an orphan only when libC is removed. Strictly speaking, this is correct. However, in practice, what we really want I believe is to get a list of orphans and their dependencies. Otherwise, one needs to do the following to get rid of all unnecessary packages: $ apt-get remove App $ deborphan libB $ apt-get remove libB $ deborphan libC $ apt-get remove libC $ deborphan libD $ apt-get remove libD I think it would be nice to be able to get this once App is removed: $ deborphan libB libC libD $ apt-get remove libB libC libD Perhaps an extra option (--recursive or --include-dependencies) would be better, but I don't really see the use of ignoring these not-technically-orphans-yet-but-still-unnecessary packages. Francois -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

