[Aptitude-devel] Bug#808882: Bug#808882: aptitude: restore reasonable ordering of package dependencies
Manuel A. Fernandez Montecelo
manuel.montezelo at gmail.com
Thu Jan 21 20:27:48 UTC 2016
Control: tags -1 + pending
Hi,
2015-12-24 15:45 Christoph Anton Mitterer:
>
>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
This is commited now, marking as +pending.
BTW the code worked in this way since forever within aptitude, so no
recent change explains it. With aptitude from last stable appears to
show them in the order of the enum values (which is mostly acceptable,
except that more people would put Recommends before Suggests, perhaps
PreDepends before Depends, as you do above):
enum DepType {Depends=1,PreDepends=2,Suggests=3,Recommends=4,
Conflicts=5,Replaces=6,Obsoletes=7,DpkgBreaks=8,Enhances=9};
(Obsoletes, I learnt, is from apt-rpm world)
...while in current unstable appears to be random.
Maybe there was some change in recent libapt, from using a ordered-like
container (std::vector or std::map) to a std::unordered_map (hash), for
example.
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montezelo at gmail.com>
More information about the Aptitude-devel
mailing list