apt/CMakeLists.txt, branch 1.4.2

Release 1.4.2

2017-05-04T20:57:12Z

Release 1.4.1

2017-04-24T16:48:35Z

Release the April Fools' release

2017-04-01T19:43:23Z

Release 1.4~rc2

2017-02-22T15:03:03Z

CMake: Install statvfs.h to include/sys, not just include/

2017-02-12T13:52:22Z

We are including sys/statvfs.h, not statvfs.h, so make sure our dummy in the correct spot.

Release 1.4~rc1

2017-02-06T13:41:36Z

Release 1.4~beta4

2017-01-17T14:20:06Z

We are basically frozen now, but (a) this wildcard thing is a bit "explosive" to call this RC and (b) you never know if you might need to add a new tiny feature and freeze can be long...

CMake: Find the Perl executable, and use it to run perl scripts

2017-01-17T00:43:50Z

This is somewhat more portable than just hardcoding perl or in the triehash case /usr/bin/perl in the shebang. Thanks: Guillem Jover for the hint Gbp-Dch: ignore

Read dpkg tables to handle architecture wildcards

2017-01-17T00:43:50Z

Our implementation of wildcards was rudimentary. It worked for some common ones, but it was also broken: For example, armel matched any-armel, but should match any-arm. With this commit, we load the correct tables from dpkg. Supported are both triplets and quadruplet tables (the latter introduced in dpkg 1.18.11). There are some odd things we have to deal with in the cache filter for historical and API reasons: * The character "*" must be accepted as an alternative to any - in fact it may appear anywhere in the wildcard as we also allow fnmatch() style wildcard matching on the commandline. * The code might get passed an arch with a minus at the end, for example the cmdline "install apt:any-arm-" will first try to check if any-arm- is a valid architecture. We deal with this by rejecting any wildcard ending in a minus. * Triplets are actually implemented by extending them to faux quadruplets - by prepending a "base" component for the architecture tuple, and "any" if there is a wildcard component. Once we have constructed a wildcard, it is transformed into an fnmatch() expression for historical reasons. In the future, we should really get a tuple class and implement matching in a better, more explicit way. This does for now though - it passes all the test cases and accepts all things it should accept. Closes: #748936 Thanks: James Clarke for the initial patch

Release 1.4~beta3

2017-01-05T19:52:03Z