| 1 |
On Sun, 2 Jan 2011 00:08:34 -0500 |
| 2 |
Mike Frysinger <vapier@g.o> wrote: |
| 3 |
|
| 4 |
> On Saturday, January 01, 2011 23:09:11 Enrico Weigelt wrote: |
| 5 |
> > BTW: several blog/maillist postings talked about the problem that |
| 6 |
> > even on recompile, older library versions could be linked in even |
| 7 |
> > on recompile. |
| 8 |
> |
| 9 |
> you'll need to provide an actual example. i have yet to see one. |
| 10 |
|
| 11 |
Not exactly the same thing, but the recent spidermonkey bump changed the lib |
| 12 |
from libjs.so to libmozjs.so. mediatomb kept finding the old libjs on |
| 13 |
rebuild. I had to uninstall mediatomb to dump the library and reinstall it. |
| 14 |
|
| 15 |
There's not much we can do about stuff like that, but it's not an uncommon |
| 16 |
occurrence. I usually run into a sticky preserved lib or two every couple |
| 17 |
months. |
| 18 |
|
| 19 |
I still think it's much better than the current portage 2.1 behavior which |
| 20 |
results in a broken mediatomb. I'll take the rare possibility of a symbol |
| 21 |
collision over a guaranteed broken package any day. |
| 22 |
|
| 23 |
|
| 24 |
-- |
| 25 |
fonts, gcc-porting, it makes no sense how it makes no sense |
| 26 |
toolchain, wxwidgets but i'll take it free anytime |
| 27 |
@ gentoo.org EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662 |
Archives