Chris Hofstaedtler wrote... > please remove deborphan. It is stuck, featurewise, in a very old time > and does not support many currently available dpkg features properly > (multi-arch, versioned provides, etc).
FWIW, deborphan is part of my regular workflow, and while you claim
it has defects, it works for me pretty well.
> Given the C codebase and lack of any patches so far I do not see that
> deborphan will ever get these features, and we have other tools
> available that work, do not mess with dpkg internals and are actually
> maintained.
One day I'm going to propose to make the following a policy about
removing a package: A phrase like "alternatives exist" without further
explanation should result in an immediate -done/wontfix for lack of
information. As this is in violation of the social contract #4.
So: What are the alternatives? How do they work? Are they a drop-in
replacment or do they introduce new dependencies? Are there feature that
will be no longer supported?
Leaving users in the void about this is just bad style.
Christoph
signature.asc
Description: PGP signature
