| 1 |
On Sun, 01 Apr 2012 17:04:11 +0100 |
| 2 |
Steven J Long <slong@××××××××××××××××××.uk> wrote: |
| 3 |
> Ciaran McCreesh wrote: |
| 4 |
> > No, what I actually say is *why* things don't work, and if it hasn't |
| 5 |
> > already been explained, I say how to fix it. |
| 6 |
> Oh? Where on Earth did you do that in this thread? All you've said so |
| 7 |
> far is that preserve-libs is "an awful hack that doesn't really work, |
| 8 |
> is conceptually unsound and that breaks all kinds of things in subtle |
| 9 |
> ways." No reasoning given whatsoever. Nor any indication of how to |
| 10 |
> fix anything. |
| 11 |
|
| 12 |
preserve-libs has been discussed to death previously and elsewhere. The |
| 13 |
changes needed to implement it correctly were included in the original |
| 14 |
EAPI 3, but were dropped due to lack of Portage implementation. There's |
| 15 |
no need to repeat the whole discussion here. |
| 16 |
|
| 17 |
-- |
| 18 |
Ciaran McCreesh |
Archives