| 1 |
grep prelink /usr/lib/portage/pym/portage.py |
| 2 |
gives lots of crap ... |
| 3 |
|
| 4 |
So it is still there! In fact there is a trivial patch waiting to be |
| 5 |
merged for prelink. So portage is prelink enabled, it just does not run |
| 6 |
the prelink command automatically . |
| 7 |
|
| 8 |
This was because prelink was slightly buggy and could not be relied on |
| 9 |
the succeed and took too long to run. |
| 10 |
|
| 11 |
Newer versions of prelink are much better so there could be a new case |
| 12 |
to make portage run prelink after a (un)merge automatically. |
| 13 |
|
| 14 |
But I cannot be bothered to push the idea (laziness). |
| 15 |
|
| 16 |
Stefan |
| 17 |
|
| 18 |
On Tue, 2004-09-14 at 18:06, Anthony Gorecki wrote: |
| 19 |
> Gentoo Developers and Users, |
| 20 |
> |
| 21 |
> I haven't been able to find any pre-existing prelink functionality built into |
| 22 |
> Portage's build system, although I've heard it was present previously and was |
| 23 |
> removed. Are there any plans to re-implement that feature? |
| 24 |
> |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-dev@g.o mailing list |
Archives