apt/apt-pkg/versionmatch.h, branch 2.3.0

apt-pkg: default visibility to hidden

2020-02-26T19:34:54Z

Run unifdef -DAPT_{8,9,10,15}_CLEANER_HEADERS

2019-06-12T13:02:55Z

Remove obsolete RCS keywords

2018-05-07T11:41:31Z

Prompted-by: Jakub Wilk

Drop cacheiterators.h include

2017-07-12T11:56:05Z

Including cacheiterators.h before pkgcache.h fails because pkgcache.h depends on cacheiterators.h.

versionmatch: Extract version match checking out of Find()

2015-08-10T09:19:11Z

Refactor version matching to allow us to check if a version matches a pin. This will aid the per-version pinning implementation.

store Release files data in the Cache

2015-06-12T14:33:37Z

We used to read the Release file for each Packages file and store the data in the PackageFile struct even through potentially many Packages (and Translation-*) files could use the same data. The point of the exercise isn't the duplicated data through. Having the Release files as first-class citizens in the Cache allows us to properly track their state as well as allows us to use the information also for files which aren't in the cache, but where we know to which Release file they belong (Sources are an example for this). This modifies the pkgCache structs, especially the PackagesFile struct which depending on how libapt users access the data in these structs can mean huge breakage or no visible change. As a single data point: aptitude seems to be fine with this. Even if there is breakage it is trivial to fix in a backportable way while avoiding breakage for everyone would be a huge pain for us. Note that not all PackageFile structs have a corresponding ReleaseFile. In particular the dpkg/status file as well as *.deb files have not. As these have only a Archive property need, the Component property takes over this duty and the ReleaseFile remains zero. This is also the reason why it isn't needed nor particularily recommended to change from PackagesFile to ReleaseFile blindly. Sticking with the earlier is usually the better option.

follow method attribute suggestions by gcc

2014-03-13T12:58:45Z

Git-Dch: Ignore Reported-By: gcc -Wsuggest-attribute={pure,const,noreturn}

cleanup headers and especially #includes everywhere

2014-03-13T12:58:45Z

Beside being a bit cleaner it hopefully also resolves oddball problems I have with high levels of parallel jobs. Git-Dch: Ignore Reported-By: iwyu (include-what-you-use)

revert 2184.1.2: do not pollute namespace in headers

2011-12-12T23:54:37Z

The breakage is just to big for now, so guard the change with #ifndef APT_8_CLEANER_HEADERS and be nice to library users

do not pollute namespace in the headers with using (Closes: #500198)

2011-09-19T11:31:29Z