Re: Automatic Debug Packages
Josselin Mouette <firstname.lastname@example.org> writes:
> Le mardi 11 août 2009 à 13:03 -0700, Russ Allbery a écrit :
>> * These packages are normal Debian packages with normal package metadata,
>> but will generally have a symlink in /usr/share/doc/<package> pointing
>> to the package for which they provide debugging information.
> Actually I don’t see the point in this symlink. It only makes things
> more complicated, especially if there is no one-to-one mapping between
> ddebs and debs.
Without the symlink, they're not valid Debian packages. It seems like a
small price to pay for keeping them consistent with the rest of Policy.
>> * What about contrib and non-free packages? Do they just lose here?
> How about yes?
I'm okay with that as an answer. I just want to document it if so.
> If we use build IDs (and this has quite some advantages, like being able
> to do more than just dump the ddebs on a repository), this can lead to
> having the same detached debugging symbols in two binary packages, since
> sometimes a binary is built twice the same exact way and put in two
> different binary packages.
Hm, really? The toolchains that I'm familiar with basically never produce
the same binary twice; something is always slightly different from
timestamp information. Could you give an example of such a case in the
archive right now where identical binaries are in multiple packages so
that I can better understand how this happens?
> The consensus on #debian-dak when we discussed this specific issue was
> to use one ddeb for each source package by default, and to let the door
> open to the maintainer overriding this default with several ddebs in a
> source, using a new header in the control file. This way we can keep
> things as simple as possible, without losing the possibility to handle
> corner cases that will arise.
In this case, I believe that, in order to comply with some of our
DFSG-free licenses, we will have to ship a copyright file in the debug
Also, some source packages are *huge*, and I don't want to have to install
50GB of debugging information for, say, all of KDE just because I want the
debugging symbols for a single library. I suppose that's why you have the
escape clause of letting maintainers do it differently if they desire, but
there I really would like to see us treat the entire archive identically
if at all possible.
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>