When displaying its conflict resolution screen, dselect lists conflicts,
dependencies, provides, etc., but does not mention replaces. It may seem
odd to the user that, for example, one required package conflicts with
another required package. If they've had some past experience with this,
they may realise that one package is obsolete and the other is its
replacement, but then there's the question of which is which. :-) Sure,
you can find the "replaces" information by toggling through the information
screens, but I feel it would be much more obvious what was going on if the
"interrelationships affecting <package>" portion of the screen mentioned the
"replaces" relationship.
An example:
--------------------------------------------------------------------------------
dselect - recursive package listing mark:+/=/- verbose:v help:?
EIOM Pri Section Package Description
n* Req base update daemon to periodically flush filesystem buffers.
**- Req base bdflush
[...]
--------------------------------------------------------------------------------
update not installed; install (was: new package). Required
update conflicts with bdflush
[...]
interrelationships affecting update
--------------------------------------------------------------------------------
Note that the entry for update in the Packages file includes the line:
replaces: bdflush, miscutils
How I think it should look:
--------------------------------------------------------------------------------
dselect - recursive package listing mark:+/=/- verbose:v help:?
EIOM Pri Section Package Description
n* Req base update daemon to periodically flush filesystem buffers.
**- Req base bdflush
[...]
--------------------------------------------------------------------------------
update not installed; install (was: new package). Required
update conflicts with bdflush
update replaces bdflush
[...]
interrelationships affecting update
--------------------------------------------------------------------------------