From: Brian Harring <ferringb@gentoo.org>
To: gentoo-dev@lists.gentoo.org, gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] stripping implementation in portage
Date: Mon, 22 Aug 2005 17:38:49 -0500 [thread overview]
Message-ID: <20050822223849.GW10816@nightcrawler> (raw)
[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]
Hola all.
Short version, the nostrip feature is a bit funky as an option. What
I'm after is effectively building all packages *with* debugging
information as default, and leaving it up to the repository you're
merging the package to, to decide on stripping or not.
IOW, if you prefer stripped binaries on your livefs, the stripping occurs
while merging to the livefs- this leaves you the option
of having binpkgs that *do* carry non-stripped binaries/libs.
Situation can be reversed also, for the embedded crowd.
Downside, for people who flat out want stripping across the board,
it's a bit more flipping it on, although that's addressed via inherit
support within the underlying config (just take my word on that one :)
Also involves a bit more logic, but that's just implementation voodoo.
So... thoughts? I'd be particularly curious about any package where
this wouldn't be viable.
Aside from that, cc'ing both lists, would prefer the discussion on dev
since the implementation can go either way; preference of if that
flexibility is desired or not is a user thing, so we discuss it in
their ml.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2005-08-22 22:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20050822223849.GW10816@nightcrawler \
--to=ferringb@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=gentoo-portage-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