apt/apt-private/private-json-hooks.cc, branch 2.5.2Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.5.22022-05-07T08:45:44ZInclude our config.h in all C++ files to avoid ODR violations2022-05-07T08:45:44ZDavid Kalnischkiesdavid@kalnischkies.de2022-04-22T15:05:36Zurn:sha1:320245536a7ad21606286d9dcf54acf3bdf096c6
Some of our headers use APT_COMPILING_APT trickery to avoid exposing too
broadly details we don't want external clients to know and make use of.
The flip-side is that this can lead to different compilation units
seeing different definitions if they aren't all using the same config.
Remove unused public zlib include from libapt fileutl.h2022-05-07T08:45:44ZDavid Kalnischkiesdavid@kalnischkies.de2022-04-21T01:01:22Zurn:sha1:8fd65748589bb1e0b671d4a291521bfba1664c5c
Our public interface doesn't use zlib for quite a while now so lets drop
the last remnants as hopefully nobody depends on us bringing it in…
Unlike our own private lib for transitive provision of unistd.h.
References: 680b916ce7203a40ebd0a3882b9a71ca77278a67
Temporarily Revert "2.3-only: Warn that the 0.1 protocol is deprecated"2021-04-29T08:42:59ZJulian Andres Klodejulian.klode@canonical.com2021-04-29T08:42:59Zurn:sha1:b60cda7992d316123b036a4a0eb5f472d21e9cdd
This reverts commit 64127478630b676838735b509fec5cdfa36874c8.
2.3-only: Warn that the 0.1 protocol is deprecated2021-04-23T10:26:46ZJulian Andres Klodejulian.klode@canonical.com2021-04-23T09:39:15Zurn:sha1:64127478630b676838735b509fec5cdfa36874c8json: Hook protocol 0.2 (added upgrade,downgrade,reinstall modes)2021-04-23T10:26:46ZJulian Andres Klodejulian.klode@canonical.com2021-04-23T09:37:28Zurn:sha1:80dd1447595c536d31912c486ac5e96f983ccc7a
Hook protocol 0.2 makes the new fields we added mandatory, and
replaces `install` mode with `upgrade`, `downgrade`, `reinstall`
where appropriate.
Hook negotiation is hacky, but it's the best we can do for now.
Users are advised to upgrade to 0.2
json: Add `package-list` and `statistics` install hooks2021-04-23T10:26:46ZJulian Andres Klodejulian.klode@canonical.com2021-04-23T08:36:18Zurn:sha1:dc11a4422d99cb49817c827b9f827617b5880600
This enables hooks to output additional information.
json: Add origins fields to version2021-04-23T10:26:46ZJulian Andres Klodejulian.klode@canonical.com2021-04-22T08:45:45Zurn:sha1:4b5215e8e2e31637cb0998ecb80d3c3146760579
Provide access to the origins of a package, such that tools
can display information about them; for example, you can write
a hook counting security upgrades.
json: Flush standard file descriptors before calling hooks2021-04-23T10:25:40ZJulian Andres Klodejulian.klode@canonical.com2021-04-23T08:34:00Zurn:sha1:0ed07360cd7e229cb458580de1f349d5d9f3568b
This ensures messages are displayed in the correct order.
json: Encode NULL strings as null2021-04-23T10:25:40ZJulian Andres Klodejulian.klode@canonical.com2021-04-21T10:21:41Zurn:sha1:b5211b9b213273c642a790ae3c3f3bbe1a4cf51e
This is the only nullable thing we have here.
json: Actually pop states2021-04-23T10:25:40ZJulian Andres Klodejulian.klode@canonical.com2021-04-21T10:17:55Zurn:sha1:09e3c0c855e339216784a1d43715c3ae2d79ec23
The JSON encoder only looked at the top state, but did not
pop it, so if we nested objects, we got stuck in whatever
the last state we pushed aside was, so in our example, we
wrongly get a comma inserted _after_ key "b":
{"a":[{}],
"b":,[{}]
}