From: bn <brullonulla@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: libtool 2.x upgrade
Date: Fri, 26 Feb 2010 11:54:59 +0100 [thread overview]
Message-ID: <4B87A883.3070108@gmail.com> (raw)
In-Reply-To: <hm7ccd$9jc$1@dough.gmane.org>
Nikos Chantziaras ha scritto:
> On 02/26/2010 03:15 AM, bn wrote:
>> Hi,
>>
>> I have a stable x86 system that requires still a bit of updating, among
>> those libtool and gcc. Since I need the system to be usable *now* for
>> work reasons, I don't feel like updating gcc and rebuilding it all with
>> an emerge -e system / emerge -e world, but more and more packages want
>> to upgrade to libtool 2.x
>>
>> Is it safe to upgrade libtool without (1)rebuilding gcc too and
>> (2)rebuilding system/world?
>
> I don't know, but for this type of scenario you are better off building
> binary packages of everything that need to be updated without actually
> installing any of it on the machine. At the end, when all binaries have
> been created by portage, you can install them in one go at a convenient
> point.
>
> Look up the "--buildpkgonly" option of emerge for this.
Looks like an excellent suggestion, I didn't think of that. Thanks!
Anyway, if someone else knows the answer to the libtool question, I'd be
happy, if only for learning purposes :)
m.
next prev parent reply other threads:[~2010-02-26 12:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-26 1:15 [gentoo-user] libtool 2.x upgrade bn
2010-02-26 2:41 ` [gentoo-user] " Nikos Chantziaras
2010-02-26 10:54 ` bn [this message]
2010-02-26 3:25 ` [gentoo-user] " Philip Webb
2010-02-26 9:07 ` Neil Bothwick
2010-02-26 13:33 ` bn
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=4B87A883.3070108@gmail.com \
--to=brullonulla@gmail.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