apt/apt-pkg/pkgcache.h, branch 1.1.exp11Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=1.1.exp112015-08-16T15:25:51ZMake 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
link DependencyData structs together2015-08-10T15:27:58ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-14T11:41:11Zurn:sha1:b291aa59ee63983204d8aeb166c388b1f97edce7
Cache generation needs a way of quickly iterating over the unique potion
of the dependencies to be able to share them. By linking them together
we can reduce the speed penality (~ 80%) with only a small reduction in
saved size (~ 20%).
Git-Dch: Ignore
split-up Dependency struct2015-08-10T15:27:18ZDavid Kalnischkiesdavid@kalnischkies.de2015-07-13T14:28:21Zurn:sha1:71c9e95b223517b5f51c4627f6ad4cce8af0d901
Having dependency data separated from the link between version/package
and the dependency allows use to work on sharing the depdency data a bit
as it turns out that many dependencies are in fact duplicates. How many
are duplicates various heavily with the sources configured, but for a
single Debian release the ballpark is 2 duplicates for each dependency
already (e.g. libc6 counts 18410 dependencies, but only 45 unique). Add
more releases and the duplicates count only rises to get ~6 for 3
releases. For each architecture a user has configured which given the
shear number of dependencies amounts to MBs of duplication.
We can cut down on this number, but pay a heavy price for it: In my
many releases(3) + architectures(3) test we have a 10% (~ 0.5 sec)
increase in cache creationtime, but also 10% less cachesize (~ 10 MB).
Further work is needed to rip the whole benefits from this through, so
this is just the start.
Git-Dch: Ignore
make all d-pointer * const pointers2015-08-10T15:25:25ZDavid Kalnischkiesdavid@kalnischkies.de2015-06-17T07:29:00Zurn:sha1:6c55f07a5fa3612a5d59c61a17da5fe640eadc8b
Doing this disables the implicit copy assignment operator (among others)
which would cause hovac if used on the classes as it would just copy the
pointer, not the data the d-pointer points to. For most of the classes
we don't need a copy assignment operator anyway and in many classes it
was broken before as many contain a pointer of some sort.
Only for our Cacheset Container interfaces we define an explicit copy
assignment operator which could later be implemented to copy the data
from one d-pointer to the other if we need it.
Git-Dch: Ignore