public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Split ELF Debug (defult or not?)
Date: Sun, 27 Nov 2005 09:50:21 -0500	[thread overview]
Message-ID: <1133103021.21175.431.camel@localhost> (raw)
In-Reply-To: <46059ce10511270639sd5540d9l75c6391082597cde@mail.gmail.com>

On Sun, 2005-11-27 at 09:39 -0500, Dan Meltzer wrote:
> On 11/27/05, Diego 'Flameeyes' Pettenò <flameeyes@gentoo.org> wrote:
> > On Sunday 27 November 2005 00:10, Luca Barbato wrote:
> > > It's great!
> > > Make it a FEATURE default on for common profiles.
> > +1, and it would be better if the FEATURES, instead of removing the generated
> > files, would disable the building of them completely, mainly because "work"
> > systems with limited CPU, RAM and HDD space would probably prefer not having
> > to create and store them :)
> 
> Err, maybe I am incorrect, but isn't it more "work" to ungenerate them
> (using strip) then to just not install them?

it's pretty easy to add a check to the save_elf_debug function to tell 
it to return if we decide that FEATURES=splitdebug will be the default 
and that if it's not set to simply return from the function without 
doing anything.


-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux

-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2005-11-27 14:55 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-26 17:50 [gentoo-dev] Split ELF Debug (defult or not?) Ned Ludd
2005-11-26 18:30 ` Bruno
2005-11-26 18:55   ` [gentoo-dev] Split ELF Debug (default " Ned Ludd
2005-11-27  9:53     ` Kevin F. Quinn
2005-11-27 12:18       ` Ned Ludd
2005-11-26 19:15 ` [gentoo-dev] Split ELF Debug (defult " Olivier Crête
2005-11-26 19:20 ` [gentoo-dev] " R Hill
2005-11-27 12:24   ` [gentoo-dev] Re: Split ELF Debug (default " Ned Ludd
2005-11-27 13:09     ` Ivan Yosifov
2005-11-27 13:32       ` Edward Catmur
2005-11-27 13:40       ` Ned Ludd
2005-11-27 15:22         ` Edward Catmur
2005-11-27 15:44           ` Ned Ludd
2005-11-27 16:55             ` Ned Ludd
2005-11-27 21:01               ` Ivan Yosifov
2005-11-27 22:24                 ` Ned Ludd
2005-11-28 11:00                 ` Paul de Vrieze
2005-11-27 18:03         ` Mark Loeser
2005-11-27 19:51           ` Olivier Crête
2005-11-26 19:22 ` [gentoo-dev] Split ELF Debug (defult " Ivan Yosifov
2005-11-26 20:01 ` Mike Frysinger
2005-11-26 21:42 ` Petteri Räty
2005-11-27  0:48   ` Dan Meltzer
2005-11-27  0:53     ` Mart Raudsepp
2005-11-27 12:23   ` [gentoo-dev] Split ELF Debug (default " Ned Ludd
2005-11-26 23:10 ` [gentoo-dev] Split ELF Debug (defult " Luca Barbato
2005-11-27 12:54   ` Diego 'Flameeyes' Pettenò
2005-11-27 14:39     ` Dan Meltzer
2005-11-27 14:49       ` Diego 'Flameeyes' Pettenò
2005-11-27 14:50       ` Ned Ludd [this message]
2005-11-27 15:31       ` Edward Catmur
2005-11-28  1:18     ` Georgi Georgiev
2005-11-28  4:21       ` Edward Catmur
2005-11-27 15:04 ` Tavis Ormandy
2005-11-27 15:30   ` Dan Meltzer
2005-11-28 11:14     ` Paul de Vrieze
2005-11-27 22:35 ` Spider (D.m.D. Lj.)
2005-11-28 10:51 ` Paul de Vrieze

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=1133103021.21175.431.camel@localhost \
    --to=solar@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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