Hey. The view was the in the curses interface, when you go from the Package View and select the details view (via Enter/Retur) of a certain package. Guess that's what you call "TUI Dependencies view".
I just tried to find (within one session) packages where the order was different - without success. So either my observation was simply wrong yesterday or it just changed. Right now I see that order (AFAICS): PreDepends Depends Conflicts Breaks Recommends Suggests Enhances Replaces (haven't checked for Provides) IMHO, those who are most likely to be interesting, should be listed first, which would be IMHO: Depends Recommends Suggests I have no strong opinion whether Pre-Depends should be before that list or after. Since it's already named "pre" and since this is the strongest class of depending, it should probably be listed first,... but OTOH, pre- dependencies are usually already fulfilled on most systems, since they're typically such standard packages like adduser, which are "simply there". Therefore they're less interesting in the view, and one could argue to have it after Suggests. Conflicts/Breaks are IMHO the least interesting, at least wrt aptitude, because *if* one of them applies, one anyway gets the red lines in the UI. As for your suggested order: Conflicts Breaks Replaces Provides I think Provides is "similar" to Enhances, so these two should IMHO go together... Enhances I'd consider close to Suggests. Replaces I'd consider to be "closest" to Conflicts/Breaks So maybe an overall of: PreDepends Depends Recommends Suggests Enhances Provides Replaces Conflicts Breaks (whether Conflicts or Breaks is first, I don't have a strong opinion). Ideally of course, that would be just a default order and people could configure it ;-) Thanks, Chris.
smime.p7s
Description: S/MIME cryptographic signature