Bug#218995: Patch for #218995
On 27 September 2012 00:58, David Kalnischkies
<kalnischkies+debian@gmail.com> wrote:
>> … because it seemed to me that the distinction is that CompType is a
>> natural representation, and CompTypeDeb is for machine parsing. ?
>
> Kinda, but I think the not-availability of CompTypeDeb from DepIterator
> makes the behavior of CompType unexpected. I might be biased here,
> but I made this mistake myself at least once while working on EDSP.
True. Though DepIterator does not provide a
deb-compatible/machine-parsable DepType.
>
> "Suddenly" returning UTF-8 characters in a char* will be even more
> unexpected. So while I think a pretty-print function might be nice,
> it shouldn't be (the default mode of) CompType().
Perhaps, though we already expect locale-specific strings from it's
peers DepType and Priority.
>
> Beside that I am not sure if the operator ≤ is better than <= for users
> in a console application like apt-get -- but maybe in T- and GUIs.
> Anyway, I think this is the topic of a different discussion after wheezy.
Yes, why I haven't mentioned it before. I will probably persue this later :-)
Reply to: