Bug#971680: /usr/share/gcc-10/python/ should go in a dev package
On Mon, Oct 05, 2020 at 10:22:49PM +0200, Matthias Klose wrote:
> On 10/5/20 8:35 PM, Josh Triplett wrote:
> > On Mon, Oct 05, 2020 at 12:08:28PM +0200, Matthias Klose wrote:
> >> On 10/5/20 10:39 AM, Josh Triplett wrote:
> >>> On Mon, Oct 05, 2020 at 09:32:28AM +0200, Matthias Klose wrote:
> >>>> On 10/4/20 11:09 PM, Josh Triplett wrote:
> >>>>> libstdc++6, installed on every system due to dependencies, contains
> >>>>> various Python scripts for GDB under /usr/share/gcc-10/python/ . These
> >>>>> scripts should go in a dev package, not in a library package.
> >>>>
> >>>> There's no part in the policy that requires debugging scripts to be part of the
> >>>> development package, and I think it's not very intuitive. There's also no
> >>>> advocated policy if these scripts should be part of a dbgsym package, and
> >>>> there's no debhelper support to add these files to a dbgsym package. So yes, I
> >>>> think the library package is the correct package to have these files. It makes
> >>>> the library package a little bit bigger, but these don't hurt there.
> >>>
> >>> There's precedent for things related to debugging a particular library
> >>> going into the -dev package for that library. For example,
> >>> /usr/share/gdb/auto-load/lib/x86_64-linux-gnu/libpthread-2.31.so-gdb.py
> >>> lives in libc6-dev, not in libc6.
> >>
> >> these were only added later than the libstdc++6 ones, so no precedence.
> >
> > I mean that it's precedent for putting debug-related things in -dev
> > packages, not that it came before libstdc++6 specifically. Would it be a
> > *problem* to put these files in the -dev package?
>
> usually people are used to to install the -dbg packages for debugging. How
> would you tell people when to install all corresponding -dev packages?
That's fair.
If you think it makes sense for library-specific gdb extensions to go in
-dbgsym packages, I think that'd be perfectly reasonable; then, when you
install all the dbgsym packages for the libraries a program links to (or
for installed libraries), you'd get all the debugging extensions as
well.
And it doesn't seem like it'd be all that hard for debhelper to
learn to put /usr/share/gdb/auto-load/$library_path files into -dbgsym
packages. (You'd still have to give debhelper a hint for the additional module
libstdc++6 wants.)
I'll file a bug on debhelper asking for a feature to put
/usr/share/gdb/auto-load/$library_path into -dbgsym packages, along with
an extension point to add more files there, and then I'll block this bug
with that one.
- Josh Triplett
Reply to: