When should -dbg packages be added?
Right now we don’t really have a policy for when to add -dbg packages (at least I can’t seem to find anything)? As a result we mostly don’t use them (there are about 80 dbg packages, apparently). It’d be nice if we provided -dbg packages for more (if not all) packages to make debugging possible.
+ Without -dbg packages for a package and all of its (recursive) dependencies) it’s usually impossible to properly debug a program. Stacktraces won’t have any info for where errors occured and won’t contain function names (due to them being optimized away), making debugging via gbd/lldb or similiar somewhat impossible.
o These -dbg packages won’t take up space on the user’s setup unless he explicitly installs them (maybe we could add a dbg package which just installs them all, like doc)
- Dbg packages can be massive, especially for already big packages. This would mean that we’d need quite a bit more disk spaces on the mirrors. We could disable -dbg packages for super big packages like webkit2gtk though.
(from redmine: issue id 10603, created on 2019-06-22)
- Make debugoptimized the default for meson
- Make RelWithDebInfo the default for CMake
$pkgname-dbga default subpkg in newapkbuild