Summary: | app-portage/eix-0.30.1 perform unnecessary database reads | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Alexander Turenko <totktonada.ru> |
Component: | Third-Party Tools | Assignee: | Martin Väth <martin> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | axs, xmw |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Alexander Turenko
2014-02-01 19:08:49 UTC
The purpose of EIX_LIMIT is to save you from a huge scrolling when a query gives an unexpected long list (e.g. by a typo). The information whether only one or two packages are not shown or whether this is a huge number is rather important in such a case. Waiting for some seconds after such a typo is not so bad, especially since the time is only lost if a lot of packages would be output, i.e. only if it was really a typo. If you have to wait often for this you are doing something wrong. The alternative would be the previous hack which could not only output a completely wrong number but even output the EIX_LIMIT message if the limit is not reached. This was wrong behaviour and needed to be fixed. Sounds reasonably. If long list is result of typo, then I can type Ctrl+C and repeat with fixed request. If that not typo, then count of matched packages is likely to important. Thanks for describe you view of these cases. |