[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#407417: Confusing versioning of libstdc++6[-...]



severity 407417 minor
thanks

Ludovic Brenta writes:
> severity 407417 serious
> justification: file clashes without Conflicts between packages
> thanks
> 
> Matthias Klose writes:
> > Ludovic Brenta writes:
> >> Proposed solution 3:
> >> 1) Do not build libstdc++6-{dbg,dev,pic} from gcc-3.4 anymore.
> >
> > why?
> 
> Because we do not build libstdc++6 from gcc-3.4 anymore.

that's not a reason.

> >> 2) In gcc-defaults, build libstdc++6-{dbg,dev,pic} that, in etch,
> >>    depend on libstdc++6-4.1-{dbg,dev,pic}.
> >
> > maybe, but not anymore for etch. For a cosmetic change it's not worth
> > touching three source packages.
> 
> Actually, just two (gcc-3.4 and gcc-defaults), but I'm nit-picking.
> More importantly, I disagree that it is a "cosmetic change":
> 
> - the libstdc++6-{dbg,dev,pic} packages in the archive are unusable
>   because there is no matching libstdc++6; normally this would qualify
>   as a "grave functionality" bug.

no, that's plain wrong. It's the nature of an ABI compatible library
that newer versions "match" earlier versions.

> - the libstdc++6-{dbg,dev,pic} contain files clashing with
>   libstdc++6-4.1-{dbg,dev,pic} but do not Conflict with them; see [1].
>   I believe that that alone qualifies as a "serious policy violation"
>   bug.

wrong again. -dev and -pic packages don't conflict and can be
installed together. libstdc++6-4.1-dbg conflicts with the other -dbg
packages, which is sufficient.

> - The same file clashes apply to libstdc++5-3.3-{dbg,dev,pic}, too.

and libstdc++6-4.1-dbg conflicts with libstdc++5-dbg as well. nothing
wrong.

You may argue that the separated debug symbols make only sense in
libstdc++6-4.1-dbg, but again, that's not the only purpose of the -dbg
packages; these provide the library built with--enable-libstdcxx-debug
 as well.

> > g++-3.4 will go away in lenny. I don't see the need to introduce
> > defaults packages in gcc-defaults.
> 
> OK, that's an option too; I suggest we just drop
> libstdc++6-{dbg,dev,pic} from gcc-3.4, and modify gcc-4.1 so that its
> packages Conflict with the ones from gcc-3.3.  I'm willing to do that
> myself, in the etch branch.

I object to this change; the only thing you might consider is to
remove the separated debug symbols from libstdc++6-dbg.

  Matthias



Reply to: