public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Gianelloni <wolf31o2@gentoo.org>
To: Patrick Kursawe <phosphan@gentoo.org>
Cc: Gentoo-dev <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)"
Date: 13 Aug 2003 16:35:19 -0400	[thread overview]
Message-ID: <1060806919.19250.12.camel@vertigo> (raw)
In-Reply-To: <20030813162256.GA2183@zaphod.anachem.ruhr-uni-bochum.de>

[-- Attachment #1: Type: text/plain, Size: 807 bytes --]

On Wed, 2003-08-13 at 12:22, Patrick Kursawe wrote:
> Presence of the "prelink" program is not enough. You also have
> to run it, which takes quite some time. I would not like to have
> it automatically run after each emerge...

The idea was to add it to FEATURES.  Also, it would only prelink the
specific package that you just installed, so it would not take quite so
long.  I still see tons of problems with that, especially in the form of
prelinking libraries.  A newer version of a library would not only
require itself to be prelinked, but also any application which referred
to that library.  This is a slippery slope and is easily dealt with in
binary distributions, but quite a bit harder to accomplish on a
source-based distribution.

-- 
Chris Gianelloni
Developer, Gentoo Linux

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-08-13 20:31 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-13 13:38 [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" Philippe Lafoucrière
2003-08-13 14:07 ` brett holcomb
2003-08-13 15:03   ` Sven Vermeulen
2003-08-13 16:15     ` Alan
2003-08-13 20:30       ` Chris Gianelloni
2003-08-13 14:08 ` Chris Gianelloni
2003-08-13 14:12   ` Brad Laue
2003-08-13 14:20   ` Philippe Lafoucrière
2003-08-13 14:25     ` Philippe Lafoucrière
2003-08-13 14:32     ` Chris Gianelloni
2003-08-13 16:17       ` Alan
2003-08-13 16:22         ` Patrick Kursawe
2003-08-13 20:35           ` Chris Gianelloni [this message]
2003-08-13 20:32         ` Chris Gianelloni
2003-08-14 10:02           ` Paul de Vrieze
2003-08-13 21:15     ` FRLinux
2003-08-13 22:49       ` William Kenworthy
2003-08-14  2:04         ` Brian Jackson
2003-08-14 10:10         ` Paul de Vrieze
2003-08-14 12:30         ` Chris Gianelloni
2003-08-14 16:59           ` William Kenworthy
2003-08-14 17:38             ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentooapproach)" matt c
2003-08-14 19:22         ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" FRLinux
2003-08-14 23:01           ` William Kenworthy
2003-08-13 14:24 ` David Holm
2003-08-13 14:28   ` Philippe Lafoucrière
2003-08-13 16:16     ` Eric Olinger
2003-08-13 19:00   ` Jon Portnoy
2003-08-13 20:02     ` Mike Frysinger
2003-08-14  1:07       ` [gentoo-dev] 'Distro Day (Measuring the benefits of the Gentoo approach)' donnie berkholz
2003-08-14  1:13         ` Jon Portnoy
2003-08-14 11:01         ` Chris Gianelloni
2003-08-13 14:34 ` [gentoo-dev] "Distro Day (Measuring the benefits of the Gentoo approach)" Stuart Herbert
2003-08-13 14:34 ` Svyatogor
2003-08-13 17:46 ` Adam Porich

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=1060806919.19250.12.camel@vertigo \
    --to=wolf31o2@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=phosphan@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