apt/CMakeLists.txt, branch 2.1.16Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.1.162021-01-08T21:18:01ZRelease 2.1.16 - "Happy build-essential freeeze" release2021-01-08T21:18:01ZJulian Andres Klodejulian.klode@canonical.com2021-01-08T20:58:58Zurn:sha1:3f9e5bedf1c9b15db8960d2daa32f703c3cc2346Release 2.1.152020-12-27T08:58:19ZJulian Andres Klodejulian.klode@canonical.com2020-12-27T08:53:26Zurn:sha1:4215b6b2ce64f7bd0988c63c8d7d3e34833ec813Release 2.1.142020-12-15T13:07:59ZJulian Andres Klodejulian.klode@canonical.com2020-12-15T13:07:59Zurn:sha1:5afd3ff6834430bb252ce5a37686bf1481f7c590Use XXH3 for cache, hash table hashing2020-12-15T12:47:22ZJulian Andres Klodejulian.klode@canonical.com2020-12-13T20:07:03Zurn:sha1:1460eebf2abe913df964e031eff081a57f043697
XXH3 is faster than both our CRC32c implementation as well
as DJB hash for hash table hashing, so meh, let's switch to
it.
Release 2.1.132020-12-10T14:42:56ZJulian Andres Klodejulian.klode@canonical.com2020-12-10T14:42:56Zurn:sha1:e480b1b6f400ae0e2a0ecfcba1d4f51b769cad1dRelease 2.1.122020-11-23T16:53:10ZJulian Andres Klodejak@debian.org2020-11-23T16:53:10Zurn:sha1:1077af2e635df738f351d5ea3515804a4de367eaRename CMake find_package helpers to avoid developer warnings2020-11-05T08:40:50ZDavid Kalnischkiesdavid@kalnischkies.de2020-11-04T23:14:32Zurn:sha1:287912d6fc7ab0ab0b5f69a4a5260b5bf53121ba
| CMake Warning (dev) at /usr/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:273 (message):
| The package name passed to `find_package_handle_standard_args` (Berkeley)
| does not match the name of the calling package (BerkeleyDB). This can lead
| to problems in calling code that expects `find_package` result variables
| (e.g., `_FOUND`) to follow a certain pattern.
| Call Stack (most recent call first):
| CMake/FindBerkeleyDB.cmake:57 (find_package_handle_standard_args)
| CMakeLists.txt:83 (find_package)
| This warning is for project developers. Use -Wno-dev to suppress it.
And indeed, we checked for BERKLEY_DB_FOUND which was not defined so our
HAVE_BDB was not set – just that it is never used, so it wasn't noticed.
Release 2.1.112020-10-21T10:01:33ZJulian Andres Klodejulian.klode@canonical.com2020-10-21T10:01:04Zurn:sha1:5d4a9e4b595ec145cdbe30b4f43d6bcdf9f26b2eRelease 2.1.102020-08-11T12:34:13ZJulian Andres Klodejulian.klode@canonical.com2020-08-11T12:34:13Zurn:sha1:6b3fbe9d5e661a3f371eb26631b3f8b502c390a6Release 2.1.92020-08-10T12:16:47ZJulian Andres Klodejulian.klode@canonical.com2020-08-10T12:16:47Zurn:sha1:f21440f5af98e1b5987e040a8f25bc3c2d6b7831