From: Nick Clifton <nickc@redhat.com>
To: Jim Blandy <jimb@redhat.com>
Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: RFC: Support for separate debug info files
Date: Wed, 11 Jun 2003 14:15:00 -0000 [thread overview]
Message-ID: <m3y9084sb7.fsf@redhat.com> (raw)
In-Reply-To: <20030611134326.GA13158@nevyn.them.org> (Daniel Jacobowitz's message of "Wed, 11 Jun 2003 09:43:26 -0400")
Hi Daniel,
>> > My theory is that the only benefit gained by being able to ship a
>> > stripped debuginfo file as opposed to an unstripped one is that it
>> > reduces the shipping size, making a distribution smaller. I am
>> > assuming that hard disk space is not really an issue, just the size
>> > of the shipped binaries.
>>
>> I think the idea is to omit the debug info files altogether from the
>> distribution. It'll make the debug info packages take longer to
>> download, but it's not a show-stopper, I think.
>
> For me it probably is a show-stopper - the issue is not download time
> or disk space, but CD size. Duplicating all the binaries we want to
> provide debug info for would probably push us over the edge. It could
> be done separately though! This will at least let us test it...
Plus you could ship the debug info CD separately. Maybe at additional
cost to the customer, or after a delay, so that the time-to-market for
a new release is reduced ?
Cheers
Nick
next prev parent reply other threads:[~2003-06-11 14:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-11 9:43 Nick Clifton
2003-06-11 13:35 ` Jim Blandy
2003-06-11 13:43 ` Daniel Jacobowitz
2003-06-11 14:15 ` Nick Clifton [this message]
2003-06-11 19:28 ` Jim Blandy
2003-06-11 13:45 ` Jakub Jelinek
2003-06-11 14:27 ` Nick Clifton
2003-06-11 17:59 ` Elias Athanasopoulos
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=m3y9084sb7.fsf@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
/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