From: Anisse Astier <anisse@astier.eu>
To: Michal Marek <mmarek@suse.cz>, linux-kbuild@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, maximilian attems <max@stro.at>
Subject: Re: [PATCH 1/2] deb-pkg: split debug symbols in their own package
Date: Fri, 3 May 2013 17:08:23 +0200 [thread overview]
Message-ID: <20130503170823.3991bb0f@serenity> (raw)
In-Reply-To: <20130419100519.485cb557@serenity>
On Fri, 19 Apr 2013 10:05:19 +0200, Anisse Astier <anisse@astier.eu> wrote :
> On Tue, 9 Apr 2013 12:05:47 +0200, Anisse Astier <anisse@astier.eu> wrote :
>
> >
> >
> > From: Anisse Astier <anisse@astier.eu>
> > Subject: [PATCH v3] deb-pkg: split debug symbols in their own package
> >
> > This can reduce almost 3 times the size of the linux-image package,
> > while keeping the debug symbols available for this particular build, in
> > their own package.
> >
> > This mimics the way kernels are built in debian, ubuntu, or with
> > make-kpkg, and comes at the price of a small slowdown in the building of
> > packages.
> >
> > v2:
> > - only build when CONFIG_DEBUG_INFO=y
> > - build debug package last.
> > - more verbose package description
> > - put package in section debug
> > v3:
> > - remove duplicate code from v2
> >
>
> What do you think ?
Any update ?
next prev parent reply other threads:[~2013-05-03 15:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-22 10:06 [PATCH 1/2] deb-pkg: split debug symbols in their own package Anisse Astier
2013-03-22 10:06 ` [PATCH 2/2] deb-pkg: add a hook argument to match debian hooks parameters Anisse Astier
2013-04-04 8:04 ` [PATCH 1/2] deb-pkg: split debug symbols in their own package Anisse Astier
2013-04-08 10:29 ` Michal Marek
2013-04-08 17:06 ` Anisse Astier
2013-04-08 17:06 ` Anisse Astier
2013-04-09 10:05 ` Anisse Astier
2013-04-19 8:05 ` Anisse Astier
2013-05-03 15:08 ` Anisse Astier [this message]
2013-05-03 15:19 ` Michal Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130503170823.3991bb0f@serenity \
--to=anisse@astier.eu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=max@stro.at \
--cc=mmarek@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.