apt/CMake, branch 2.9.18Debians commandline package managerhttps://git.kalnischkies.de/apt/atom?h=2.9.182024-12-18T09:25:24ZIntroduce automatic pager for read commands2024-12-18T09:25:24ZJulian Andres Klodejak@debian.org2024-12-16T16:05:40Zurn:sha1:6e260e26e4cd671f781151e24d89a17b29a55530
Automatically show the output of `show`, `policy`, `list`,
`search`, `showsrc` in a pager.
The pager setup is inspired by git's pager setup. Notably,
the pager is found using APT_PAGER and PAGER variables.
We wait for the pager to be setup somewhat correctly by
using a notify pipe to figure out whether execvp() was
succesful - then the pipe will read EOF as the other end
got closed by CLOEXEC during exec - or not, then the pipe
will contain an errno.
We set up the correct handlers for signals and exit to close
the fds and wait for the pager. Notably inside the signal
handler we cannot flush our streams, only close them, so
there is some duplication.
We call the InitOutputPager() function from inside the
various Do...() functions rather than setting it up
generally in InitOutput(). Doing so allows us to first
render the progress without a pager, and then setup
the pager for the content only which improves user
experience.
When we setup a pager we also take care to disable
standard input, as we should not be prompting users
while a pager is running (the pager will be reading
from the tty directly). We do this by dup2-ing() a
/dev/null over it; if we just close()d the fd, another
open() might reuse the fd number and problems could
occur.
Avoid unnormalized paths for CMake install destinations2024-11-22T12:11:13ZDavid Kalnischkiesdavid@kalnischkies.de2024-11-19T21:58:13Zurn:sha1:7578b7031921231400be78fa8c2893bbd5ea18df
CMake 3.31 is very noisy about our manpage (and to a lesser extend
documentation in general) building as we used "//" and "/../" there.
`cmake --help-policy CMP0177` documents the warning, so we could just
decide on a value and deal with it, but given our usage is not really
needed and rather trivial to change lets not pick a value and instead
use a normalized path so we don't use different code paths in CMake
depending on which CMake version we happen to be build with.
Do not ignore if a cmake execute_process fails2024-04-24T13:16:21ZDavid Kalnischkiesdavid@kalnischkies.de2024-04-05T14:02:39Zurn:sha1:3e24f431d9527816820e103df7db9f39062b551d
Ignoring errors might lead to failures later on anyhow, but especially
with triehash it could also lead to broken builds or other crazy stuff,
so lets better be save than sorry.
Hide nice subtree character and indentation of summary from translations2024-04-13T19:22:36ZJulian Andres Klodejak@debian.org2024-04-13T19:22:36Zurn:sha1:cf71004551eca23f6d73648bc19f65e8b2a08ce9
Also allow us to have utf-8 characters in xgettext, but msgcomm still
fails so ugh.
This avoids translations messing up the formatting a bit more, at
least, and makes apt build again
Support building without gnutls2024-03-03T07:23:51ZSteve Langaseksteve.langasek@canonical.com2024-03-03T07:10:14Zurn:sha1:9044806c2adc6118399349c70a6c5746cedcc374
Once in a generation, it may be necessary to bootstrap apt in an
environment where gnutls is not yet available. This makes gnutls
support in apt optional.
You may also want a configure flag to force gnutls to be required from
outside the buildsystem (e.g. debian/rules).
Only accept installs of usrmerge on unmerged-usr systems2023-09-16T10:37:31ZJulian Andres Klodejulian.klode@canonical.com2023-09-16T10:34:48Zurn:sha1:99c888b5eabbb7008bf4451bc62c277f28bb925f
As of bookworm, merged-usr is mandatory, and people got caught
in the crosshairs of the dpkg fsys-unmessusr debacle and inadvertently
reverted back to an unmerged configuration and continue to remain
on an unsupported system unknowingly.
Help them by erroring out when they are installing packages on /,
they are not in a chroot, and a usrmerge package is available.
Set our entities as dependencies in manpage generation2022-11-02T12:41:14ZDavid Kalnischkiesdavid@kalnischkies.de2022-11-02T11:40:24Zurn:sha1:acb5002a7cd03253522978e70258589e9b262216
Changes in the entities do not lead to a rebuild of the manpages
otherwise. We also try to have each lingua have its own (translated)
entities as dependencies rather than all as the old code order
would have suggested.
Gbp-Dch: Ignore
Drop SHA2 define from config as the code is gone2022-04-01T09:44:26ZDavid Kalnischkiesdavid@kalnischkies.de2022-04-01T09:29:31Zurn:sha1:d1d093713afc5ea26e75abc7c7b16d4315460a4b
We don't ship the code this define was effecting since 2020,
so defining this constant is pointless.
References: e8016805b87bead8eb3dff0d0559c5d9590b721b
Gbp-Dch: Ignore
Remove unused config check for pre-XXH3 cache hashing2021-02-03T16:36:45ZDavid Kalnischkiesdavid@kalnischkies.de2021-02-03T14:26:32Zurn:sha1:c8d65a59a36400aaf85ff96b0c813f8fc53cd8bb
References: 1460eebf2abe913df964e031eff081a57f043697
Gbp-Dch: Ignore
Use 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.