public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Heinrich Wendel <lanius@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Portage prelink patch?
Date: Thu, 16 Sep 2004 16:13:33 +0200	[thread overview]
Message-ID: <200409161613.33238.lanius@gentoo.org> (raw)
In-Reply-To: <200409161607.39441.lanius@gentoo.org>

On Thursday 16 September 2004 16:07, Heinrich Wendel wrote:
> On Wednesday 15 September 2004 16:53, Stefan Jones wrote:
> > grep prelink /usr/lib/portage/pym/portage.py
> > gives lots of crap ...
> >
> > So it is still there! In fact there is a trivial patch waiting to be
> > merged for prelink. So portage is prelink enabled, it just does not run
> > the prelink command automatically .
>
> 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?

>
> > This was because prelink was slightly buggy and could not be relied on
> > the succeed and took too long to run.
> >
> > Newer versions of prelink are much better so there could be a new case
> > to make portage run prelink after a (un)merge automatically.
> >
> > But I cannot be bothered to push the idea (laziness).
> >
> > Stefan
>
> mfg, heinrich :)
mfg, heinrich :)

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2004-09-16 14:13 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 [this message]
2004-09-16 15:52       ` Stefan Jones
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=200409161613.33238.lanius@gentoo.org \
    --to=lanius@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