From: covici@ccs.covici.com
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] serious problems trying to go to new abi_x86_32 support
Date: Sat, 25 Apr 2015 06:45:16 -0400 [thread overview]
Message-ID: <16244.1429958716@ccs.covici.com> (raw)
In-Reply-To: <CAGfcS_=znc1fVomPG4zDHuT5R1MN4=dWt6JXMnV5oB7sYYxu6w@mail.gmail.com>
Rich Freeman <rich0@gentoo.org> wrote:
> On Sat, Apr 25, 2015 at 12:10 AM, <covici@ccs.covici.com> wrote:
> > Well, now that I have put abi_x86_32 in make.conf and did those 80
> > packages and fixed the preserved_libs, in my next update it wants to do
> > 199 reinstalls to get every possible package which has that flag -- do I
> > need all that or should I go back to the individual packages, now that
> > things are fixed as far as the libs are concerned? Do I gain anything
> > by having all those packages have that flagg set?
>
> That's up to personal preference. You've already found a few on this
> list telling you that you should just set it in make.conf. You won't
> have trouble finding many others (including me) who will tell you to
> just stick it in package.use when needed only.
>
> The only thing you gain is being able to run 32-bit applications
> against those libraries, even if you don't have any need to. The only
> thing you lose is a bunch of inodes, and maybe some compile time.
Well, that clarifies things a bit -- what is strange is that I had to do
about 70 packages beffore portage would let the preserved-rebuild go
through, for future reference is there an automatic way to add all the
use flags, even the packages which already have other use flags?
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?
John Covici
covici@ccs.covici.com
next prev parent reply other threads:[~2015-04-25 10:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-24 19:37 [gentoo-user] serious problems trying to go to new abi_x86_32 support covici
2015-04-24 20:19 ` Mike Gilbert
2015-04-24 20:51 ` covici
2015-04-24 21:58 ` Mike Gilbert
2015-04-24 22:09 ` covici
2015-04-24 22:12 ` Mike Gilbert
2015-04-24 22:47 ` covici
2015-04-25 4:10 ` covici
2015-04-25 10:40 ` Rich Freeman
2015-04-25 10:45 ` covici [this message]
2015-04-25 12:17 ` Neil Bothwick
2015-04-25 12:22 ` covici
2015-04-24 20:52 ` J. Roeleveld
2015-04-24 20:55 ` covici
2015-04-24 21:49 ` Neil Bothwick
2015-04-24 22:05 ` covici
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=16244.1429958716@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=gentoo-user@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