apt/apt-pkg/tagfile-order.c, branch 2.7.12Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.7.122022-04-01T12:16:19ZDo not order long obsoleted fields anymore2022-04-01T12:16:19ZDavid Kalnischkiesdavid@kalnischkies.de2022-03-28T13:47:45Zurn:sha1:2005f1c263a942b37d179b9b8f9b7ab343ca7459
The dependency relation fields old names were deprecated in 1995
as the new ones were introduced. That seems barely long enough now
as a transition period.
Drop support for long obsoleted Suggests alias: Optional2022-04-01T12:16:15ZDavid Kalnischkiesdavid@kalnischkies.de2022-03-28T13:25:36Zurn:sha1:7b8da771e2061462b9196f38366c34e4f919d0df
dpkg-dev stopped recognizing it in 2007 (1.14.7) while building packages.
The rename itself happened in 1995 (0.93.72).
Document tagfile-keys.h as internal to apt2022-04-01T12:15:26ZDavid Kalnischkiesdavid@kalnischkies.de2022-03-28T13:19:11Zurn:sha1:f6438ea9e726a1c13ce8d90ac78cc272346ab0f8
The previous regime of the file was to sort it on insert, but that
changes the values in the generated enum, which is fine as long as we
only use it in libapt itself, but breaks on other users.
The header was always intended to be private to apt itself, so we just
document this here now and lay the ground work to have the file in the
future only appended to, so that it remains sufficiently ABI stable that
we can use it outside the library in our apt tools.
We also remove some fields apt is unlikely to need or only uses in
certain cases outside of any (speed) critical path to have enough room
to add more fields soon as currently we are limited to 128 fields max
and it would be sad if we use up that allowance entirely already.
Recognize Static-Built-Using and order it below Built-Using2022-04-01T09:44:17ZDavid Kalnischkiesdavid@kalnischkies.de2022-03-26T10:29:12Zurn:sha1:889462ec33480940a355589b0ae57987f17a86e2
dpkg added a new field (see there for details) which breaks our
testcases due to an unknown field. apt doesn't make use of the field,
but we can at least order it nicely in output we generate.
References: dpkg commit 16c412439c5eac5f32930946df9006dfc13efc02
Closes: #1008759
Add basic support for the Protected field2020-06-29T15:32:17ZJulian Andres Klodejulian.klode@canonical.com2020-06-29T15:31:06Zurn:sha1:ddd8fc3d28cd8e668868158049ced7fa3c8c71b8
This will be mapped to Important for the time being.
Fix testsuite for and add new fields from dpkg 1.192017-10-20T21:40:53ZJulian Andres Klodejak@debian.org2017-10-20T21:37:36Zurn:sha1:404dececf913d3c09368a73ca00aa8172dbf6865
tagfile-order.c: Add missing fields from dpkg 1.19
For binary packages, this is Build-Essential; for source packages,
it is Description.
test-bug-718329-...: Ignore control.tar.*, changes in dpkg 1.19
test-apt-extracttemplates: Fix for dpkg 1.19
add Auto-Built-Package to tagfile-order2017-02-09T11:59:05ZDavid Kalnischkiesdavid@kalnischkies.de2017-02-09T09:15:18Zurn:sha1:f09735bfa051b8c830b467ee8d78138c9f1aa808
Added in dpkg commit 6c8203440bf443d3031ee2ab8485b16c1b6da3b6
add Testsuite-Triggers to tagfile-order2016-07-08T10:43:55ZDavid Kalnischkiesdavid@kalnischkies.de2016-07-08T09:49:36Zurn:sha1:13a6bb6d99da52cef1d195dfe37430b549ae62db
Added in dpkg in commit 90324cfa942ba23d5d44b28b1087fbd510340502.
sync TFRewrite*Order arrays with dpkg and dak2015-05-11T15:22:32ZDavid Kalnischkiesdavid@kalnischkies.de2015-05-09T16:55:41Zurn:sha1:e8fb1cdfdd13e45f2b3abbd57a28b57ae6137f14
dpkg and dak know various field names and order them in their output,
while we have yet another order and have to play catch up with them as
we are sitting between chairs here and neither order is ideal for us,
too.
A little testcase is from now on supposed to help ensureing that we do
not derivate to far away from which fields dpkg knows and orders.