From: Robert Riebisch <rr@bttr-software.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Remove -s flag in Makefile
Date: Thu, 26 Mar 2009 22:45:52 +0100 [thread overview]
Message-ID: <49CBF790.1020504@bttr-software.de> (raw)
In-Reply-To: <49CBF6D7.6090608@redhat.com>
Gerd Hoffmann wrote:
> No. binutils and gdb can handle debuginfo being stored in separate
> files these days. The usual packaging procedure is to install
> unstripped, then split away debuginfo to separate files for a separate
> package, so you end up with one $software and one $software-debuginfo
> package. By default only $software is installed, but if needed you can
> install get debuginfo too without having to compile the package manually.
>
> I'd tend to keep the default behavior to install stripped. There should
> be an easy way out for packaging tools, they should be able to override
> the default without having to patch the Makefile(s). Some configure
> script option should do the trick.
Agreed.
Robert Riebisch
--
BTTR Software
http://www.bttr-software.de/
next prev parent reply other threads:[~2009-03-26 21:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-25 18:45 [Qemu-devel] [PATCH] Remove -s flag in Makefile Glauber Costa
2009-03-25 19:49 ` Riku Voipio
2009-03-25 19:56 ` Anthony Liguori
2009-03-26 18:34 ` Lennart Sorensen
2009-03-26 18:50 ` Avi Kivity
2009-03-26 19:02 ` M. Warner Losh
2009-03-26 19:08 ` Lennart Sorensen
2009-03-26 19:20 ` Michael Jennings
2009-03-26 19:30 ` M. Warner Losh
2009-03-26 19:48 ` Lennart Sorensen
2009-03-26 20:07 ` M. Warner Losh
2009-03-26 21:47 ` Lennart Sorensen
2009-03-26 21:09 ` Riku Voipio
2009-03-26 21:16 ` M. Warner Losh
2009-03-26 22:11 ` Riku Voipio
2009-03-26 23:11 ` M. Warner Losh
2009-03-26 21:42 ` Gerd Hoffmann
2009-03-26 21:45 ` Robert Riebisch [this message]
2009-03-26 19:19 ` Riku Voipio
2009-03-25 20:08 ` Johannes Schindelin
2009-03-25 20:26 ` M. Warner Losh
2009-03-25 20:45 ` Anthony Liguori
2009-04-03 9:27 ` Jan Marten Simons
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=49CBF790.1020504@bttr-software.de \
--to=rr@bttr-software.de \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).