Control: forwarded -1 https://github.com/log4cplus/log4cplus/issues/466 Control: severity -1 wishlist Control: tags -1 wontfix
Hi Sorin, sorry for the late reply, I missed that mail from the BTS… On Tue, 01 Dec 2020 15:43:18 +0100 Sorin Manolache <sor...@gmail.com> wrote: > 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. Reading the github issue, I have to confirm that wilx is right. Even with 1.1.x it is not safe to use when you use fork() without exec(). Actually, in a multithread application, the only robust way is to only fork() when there is an exec() followed immediatly, as fork() will _only_ clone the first thread and leave everything else in limbo (just looked that up to confirm in my copy of Kerris's The Linux Programming Interface). Thats actually a POSIX thing, not liblog4cplus. (So a valid usecase would be programms that forking but are single-threaded otherwise.) I do not plan to maintain a second liblog4cplus version in Debian, but the current setup should not prevent you to become maintainer of package for the old version yourself. For sure we can arrange things that both versions can coexists (I didnt check if it is possible to have both dev packages coinstallable, but we can certainly find a solution if you want to becoming the maintainer. Feel free to approach me then!) (I'm tagging it for now wontfix, as there is little I can do right now.) Cheers, tobi
