Re: When does a conflict become outdated?
Am Mi, den 31.03.2004 schrieb Matt Zimmerman um 20:29:
> > Why? What harm is it doing? And don't say "bloat": the space taken by
> > all the outdated conflicts combined could be easily compensated for
> > by removing, say one IRC client. Or one editor. Or one module from
> > xscreensaver.
> It degrades the readability of the dependency relationships, and distracts
> the maintainer from the important ones.
I do not remember offhand, but IIRC we _ensure_ upgrade paths only from
one version to a subsequent one. So anything beyond this is a bonus for
the maintainer to decide. I agree that removing cruft from the
dependencies improves readability and should thus be considered by
Fingerprint: A46A 753F AEDC 2C01 BE6E F6DB 97E0 3309 9FD6 E3E6