From: Stefan Jones <cretin@gentoo.org>
To: Heinrich Wendel <lanius@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Portage prelink patch?
Date: Thu, 16 Sep 2004 08:52:22 -0700 [thread overview]
Message-ID: <1095349941.7736.2.camel@saj.multigig> (raw)
In-Reply-To: <200409161613.33238.lanius@gentoo.org>
On Thu, 2004-09-16 at 07:13, Heinrich Wendel wrote:
> > Since it is a trivial patch I hope you can get it in for portage-2.0.51.
>
> Is this http://bugs.gentoo.org/show_bug.cgi?id=63563 or is there another patch
> which automatically prelinks new installed binaries/libraries?
>
That is the pending trivial patch.
Making portage automatically prelink binaries and libraries in my
opinion is non trivial, as there is a large impact in portage
performance and things can go wrong easily.
It is doable if anyone wants to develop it, just not me.
Stefan
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-09-16 15:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-15 1:06 [gentoo-dev] Portage prelink patch? Anthony Gorecki
2004-09-15 14:53 ` Stefan Jones
2004-09-16 14:07 ` Heinrich Wendel
2004-09-16 14:13 ` Heinrich Wendel
2004-09-16 15:52 ` Stefan Jones [this message]
2004-09-15 16:42 ` Lisa Seelye
2004-09-15 17:06 ` Stefan Jones
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=1095349941.7736.2.camel@saj.multigig \
--to=cretin@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=lanius@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