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

Bug#365349: Add support for creating a "debuginfo" package



On Wed, Jul 15, 2009 at 08:36:27PM +0200, Bastian Blank wrote:
> On Wed, Jul 15, 2009 at 10:45:23AM -0600, John Wright wrote:
> >  install-image_$(ARCH)_$(FEATURESET)_$(FLAVOUR)_plain:
> 
> This is not the correct target.

Can you elaborate?  Do you mean it should go in its own target?

> > +	+$(MAKE_CLEAN) -C $(DIR) modules_install INSTALL_MOD_PATH='$(CURDIR)'/$(PACKAGE_DIR) INSTALL_MOD_STRIP=1
> > +	+$(MAKE_CLEAN) -C $(DIR) modules_install INSTALL_MOD_PATH='$(CURDIR)'/$(DEBUG_DIR)
> 
> How about only installing debugging infos in the debugging package?

THis would be ideal.  Current tools like "crash" don't work with an
image that's been stripped with "--only-keep-debug".  I'm not sure what
strip is removing that crash needs, but I'll look into it.

Stripping the modules themselves with "--only-keep-debug" seems to work
with crash, but then it saves only a marginal amount of space (from 963
MB down to 926 MB on a 2.6.29 kernel).  Similarly with the vmlinux: from
69 MB down to 60 MB.  Maybe strip is just confused by something in the
format of a kernel module?

> > +Package: linux-image-@upstreamversion@@abiname@@localversion@-dbg
> > +Section: admin
> > +Priority: optional
> > +Provides: linux-image-dbg, linux-image-@major@-dbg, linux-modules-@upstreamversion@@abiname@@localversion@-dbg
> > +Pre-Depends: debconf (>= 0.2.17) | debconf-2.0
> > +Depends: module-init-tools (>= 0.9.13), coreutils (>= 5.2.1)
> 
> Are your serious?

Uhm, yes...  Why should I not be?  If you're worried about the virtual
packages it provides, I'm not partial to them.  If the patch needs
improvement, I'm glad to improve on specific points, but I don't
understand what you don't like about this section.

-- 
+----------------------------------------------------------+
| John Wright <john.wright@hp.com>                         |
| HP Mission Critical OS Enablement & Solution Test (MOST) |
+----------------------------------------------------------+



Reply to: