Package: liblog4cplus-dev Version: 2.0.5-2 Severity: normal X-Debbugs-Cc: sor...@gmail.com
Dear Maintainer, I believe that the 2.0.x version of liblog4cplus is not yet fully mature. A limitation, that I find severe, is that it does not work in a program that calls fork without calling exec immediately after. See this discussion too: https://github.com/log4cplus/log4cplus/issues/466 Therefore, I would propose that the dev-package contains the version in its name. Thus, we would have two mutually incompatible packages, for example liblog4cplus1-dev and liblog4cplus2-dev. This would allow the user choose which version he wants to install. As it is now, we can install any of the two versions of the lib (liblog4cplus-1.1-9 or liblog4cplus-2.0.5) but only the 2.0.5 version of the development files. I would like to be able to stick around for a while with 1.1.9 and write code that uses it, at least until the 2.0.x line becomes more usable. Thank you, Sorin -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.0-1-amd64 (SMP w/8 CPU threads) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages liblog4cplus-dev depends on: ii liblog4cplus-2.0.5 2.0.5-2 liblog4cplus-dev recommends no packages. liblog4cplus-dev suggests no packages. -- no debconf information
