package looking for maintainer: apitrace
https://build.opensuse.org/package/show/X11:Utilities/apitrace I created it, because once I needed to report some bug in graphic drivers. I'm not using it regularly for any work. I maintained it as long as it was quite easy. I don't have enough time and interest to keep doing it. Recently there was a new release (version 11), which added a bunch of dependencies as git submodules. It's easy to patch it to use system libraries, except for libbacktrace. I'm not sure if it should use a shared library (there's a package available in network:cryptocurrencies project, but not in Factory) or link one statically. I did some initial work here: https://build.opensuse.org/package/show/home:etamPL:branches:X11:Utilities/a...
Hi, Am Sonntag, 8. Mai 2022, 21:26:28 CEST schrieb Adam Mizerski:
https://build.opensuse.org/package/show/X11:Utilities/apitrace
I created it, because once I needed to report some bug in graphic drivers. I'm not using it regularly for any work. I maintained it as long as it was quite easy. I don't have enough time and interest to keep doing it.
Recently there was a new release (version 11), which added a bunch of dependencies as git submodules. It's easy to patch it to use system libraries, except for libbacktrace. I'm not sure if it should use a shared library (there's a package available in network:cryptocurrencies project, but not in Factory) or link one statically.
FWICT previously it was also bundled, just not as git submodule. So the simple way is to switch to an OBS _service to generate the tarball with submodules, then it should stay quite easy to keep maintained for a while again. (It's really annoying that GitHub release tarballs don't include submodules, it makes no sense...) IMO it actually makes sense to build apitrace statically, as one of the use cases is to debug third-party applications like games, which might load libraries conflicting with the one apitrace was built against. Question is whether it should link statically against the system libs we have or against the bundled sources. For libpng for instance we don't have a static version as that would make security updates harder, but in the apitrace case the input is already "trusted". For now it probably makes sense to keep it as it is, as so far it worked fine. Cheers, Fabian
I did some initial work here: https://build.opensuse.org/package/show/home:etamPL:branches:X11:Utilities/a...
participants (2)
-
Adam Mizerski
-
Fabian Vogt