| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| cmake-update-project-version.patch | cmake: update project version howardhinnant-date is at version 3.0.1, but upstream CMakeLists.txt says 3.0.0. This patch fixes it. |
Andrea Pappacoda <andrea@pappacoda.it> | yes | upstream, https://github.com/HowardHinnant/date/commit/2e19c006e2218447ee31f864191859517603f59f | 2021-09-17 | |
| Zero_initialize_local_info_in_get_info.patch | [PATCH] Zero initialize local_info in get_info * Even when the result is unique, the second sys_info should be zero initialized. |
Howard Hinnant <howard.hinnant@gmail.com> | yes | upstream | upstream, https://github.com/HowardHinnant/date/commit/b49a7575ebbe127e8bd344900a52c14b5d69dd7b | 2021-05-18 |
| When_comparing_sys_info_in_test.patch | [PATCH] When comparing sys_info in test... only compare whether the saves are equal to 0 and not their actual values. This allows one to compare against the binary database which does not contain actual values of save. |
Howard Hinnant <howard.hinnant@gmail.com> | yes | upstream | upstream, https://github.com/HowardHinnant/date/commit/052eebaf0086e6bbc5ead01c3f1a8f02496aa701 | 2021-05-18 |
| Change_default_test_mode_to_C++17.patch | [PATCH] Change default test mode to C++17 | Howard Hinnant <howard.hinnant@gmail.com> | no | upstream, https://github.com/HowardHinnant/date/commit/ebb5719cd710c694bf62d45a03b3d13f532a35d1 | 2021-05-19 | |
| test_use_pthread_when_CXX_is_g++.patch | [PATCH] test: use -pthread when $CXX is g++ Fixes https://github.com/HowardHinnant/date/issues/713 |
Andrea Pappacoda <andrea@pappacoda.it> | yes | upstream | upstream, https://github.com/HowardHinnant/date/commit/655b249b8f463f690c53a19d6b4110297699e3c5 | 2021-11-02 |
| cmake-install-all-headers.patch | cmake: install all headers Lazy solution: mark all headers as either PUBLIC_ or PRIVATE_HEADER, requiring CMake 3.15. diff --git a/CMakeLists.txt b/CMakeLists.txt index bc0bcb2..0734b5c 100644 |
Andrea Pappacoda <andrea@pappacoda.it> | not-needed | debian upstream | 2022-08-04 | |
| tests-disable-lcurl.patch | disable linking against curl in tests It is not needed, as in Debian we use the system timezone database. This also allows removing the build-dependency on libcurl-dev. |
Andrea Pappacoda <andrea@pappacoda.it> | not-needed | 2022-08-04 | ||
| Stop-using-PATH_MAX.patch | [PATCH] Stop using PATH_MAX PATH_MAX isn't guaranteed to be defined in Posix environments; it is only on systems that have a path length limit, and even in environments where it is defined its usage can lead to issues. To avoid using PATH_MAX, I've made two main changes: - Where realpath() was used, I've changed the code to use its [POSIX.1-2008]'s new behaviour, where passing a null pointer as the resolved_name buffer results in realpath() to automatically allocate a buffer large enough to handle the given path, that is returned to the caller. This has been supported for a long time as a GNU libc extension before being standardized. - Where readlink() was used, the size of the buffer was already determined when calling lstat(); the returned struct stat contains a st_size field, containing the number of bytes needed to store the symbolic link contents. This meant that to avoid using the tricky define I only needed to use a dynamically allocated buffer instead of a static one, of size stat.st_size (+1 when a null terminator is needed). To make sure that memory is always freed, I've wrapped the new dynamic allocations in an std::unique_ptr. The pointer returned by realpath() must be freed with free(), so a unique_ptr with a custom deleter that calls free() on destruction was used. To read more about why PATH_MAX leads to buggy code I'd suggest reading something like this: <https://eklitzke.org/path-max-is-tricky>. [POSIX.1-2008]: https://pubs.opengroup.org/onlinepubs/9699919799/functions/realpath.html |
Andrea Pappacoda <andrea@pappacoda.it> | yes | 2022-10-10 | ||
| cmake-has-string-view-interface.patch | build: always mark HAS_STRING_VIEW as part of the interface If the library gets compiled with HAS_STRING_VIEW=1, consumers always need to link to the functions using std::string_view, as they are the only ones compiled into the shared library. |
Andrea Pappacoda <andrea@pappacoda.it> | yes | 2022-12-21 | ||
| docs-dark-scheme.patch | Support dark color-scheme This patch updates the html documentation to add the color-scheme meta element, signalling light and dark color scheme support, and updating the inline CSS styles to override some colors when dark mode is active, to make sure that the document is always readable. |
Andrea Pappacoda <andrea@pappacoda.it> | yes | 2023-01-07 |