apt/apt-pkg/pkgcache.h, branch 1.1.6Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.1.62015-11-27T14:40:47Zadd messages to our deprecation warnings in libapt2015-11-27T14:40:47ZDavid Kalnischkiesdavid@kalnischkies.de2015-11-27T14:40:47Zurn:sha1:5dd00edbcf702cac1ea22392796c65881a8ef6f9
Git-Dch: Ignore
do not report deprecate warnings for the None declaration2015-09-14T13:22:18ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-11T12:19:16Zurn:sha1:fcffe89d8344e699267210badac53ff24dd41148
This is defined for compatibility, warning about it is intended, but
only in places where it is actually used, rather than at the place we
declare it for compatability…
Git-Dch: Ignore
remove incorrect optimization branches2015-09-14T13:22:18ZDavid Kalnischkiesdavid@kalnischkies.de2015-09-08T11:58:55Zurn:sha1:8fec289ad8a2c42350c24d5c97b0f104fbbea176
These assumptions were once true, but they aren't anymore, so what is
supposed to be a speed up is effectively a slowdown [not that it would
be noticible].
Usage of SingleArchFindPkg was nuked in a stable update already as the
included assumption was actually harmful btw, which is why we should get
right of other 'non-harmful' but still untrue assumptions while we can.
Git-Dch: Ignore
Make pkgCache::Priority() static, it does not need the instance2015-08-16T15:25:51ZJulian Andres Klodejak@debian.org2015-08-16T15:25:51Zurn:sha1:ebc5b43cca0a16e3f552130db9233fa14b313739
It still compiles after the change, so just merge it.
Closes: #448627
Drop the Section field from pkgCache::Package again2015-08-12T21:45:17ZJulian Andres Klodejak@debian.org2015-08-12T21:44:33Zurn:sha1:a1dfe33790edda246a23a5c5d3c432cd8429e848
This somehow got back, we don't really know why. Emulate the
Section() method in the PkgIterator by looking at the section
of the head of the VersionList.
Re-introduce None as a deprecated alias for No2015-08-11T11:59:15ZJulian Andres Klodejak@debian.org2015-08-11T10:01:11Zurn:sha1:f01090067bbc50312c8ac74714027da3a2f00e20
Gbp-Dch: ignore
no value for MultiArch field is 'no', not 'none'2015-08-10T15:27:59ZDavid Kalnischkiesdavid@kalnischkies.de2015-08-10T09:31:28Zurn:sha1:22df31be37d56c07ed029f5a4d5041f21070d2d6
Git-Dch: Ignore
hide implicit deps in apt-cache again by default2015-08-10T15:27:58ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-16T09:15:25Zurn:sha1:8c7af4d4c95d0423fbd0f3baa979792504f4f45f
Before MultiArch implicits weren't a thing, so they were hidden by
default by definition. Adding them for MultiArch solved many problems,
but having no reliable way of detecting which dependency (and provides)
is implicit or not causes problems everytime we want to output
dependencies without confusing our observers with unneeded
implementation details.
The really notworthy point here is actually that we keep now a better
record of how a dependency came to be so that we can later reason about
it more easily, but that is hidden so deep down in the library internals
that change is more the problems it solves than the change itself.
use a smaller type for flags storage in the cache2015-08-10T15:27:58ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-15T12:36:16Zurn:sha1:dfe66c72ffc010e019e96b35154e1ad4ab506a6e
We store very few flags in the cache, so keeping storage space for 8 is
enough for all of them and still leaves a few unused bits remaining for
future extensions without wasting bytes for nothing.
Git-Dch: Ignore
remove the compatibility markers for 4.13 abi2015-08-10T15:27:58ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-15T11:21:21Zurn:sha1:4dc77823d360158d6870a5710cc8c17064f1308f
We aren't and we will not be really compatible again with the previous
stable abi, so lets drop these markers (which never made it into a
released version) for good as they have outlived their intend already.
Git-Dch: Ignore