| 1 |
On Tuesday 29 October 2002 11:38, Kim Nielsen wrote: |
| 2 |
> On Tue, 2002-10-29 at 10:06, Sven Vermeulen wrote: |
| 3 |
> > Your missing .so-files have an other cause... |
| 4 |
> |
| 5 |
> No. |
| 6 |
> |
| 7 |
> Some files are linked to a lot of .so files .. when one files gets |
| 8 |
> renewed it gets new features and version .. when the old program is |
| 9 |
> linked to this version you don't automaticly emerge evolution for |
| 10 |
> example . You just upgrade the lib that its using. And that is the |
| 11 |
> problem I'm having. |
| 12 |
> |
| 13 |
> Otherwise you would have to remerge galeon everytime you mozilla .. |
| 14 |
> haven't you ever seen that error/message that galeon says if its linked |
| 15 |
> against an old version of mozilla ? |
| 16 |
> |
| 17 |
> /Kim |
| 18 |
|
| 19 |
The problem is downgrading. If you have had installed say libfoo-1.1. Now the |
| 20 |
developers find out that libfoo-1.1 is seriously broken. As a consequence, |
| 21 |
libfoo-1.1 is masked, and libfoo-1.0 is the newest. If you now do an emerge |
| 22 |
-u libfoo the old version is installed. But if libfoo-1.0 allready was |
| 23 |
installed it doesn't get installed. The installation of libfoo-1.0 is not |
| 24 |
complete though, because libfoo-1.1 overwrites many of its files. Now with an |
| 25 |
emerge clean libfoo-1.1 is removed, as a consequence libfoo-1.0 is crippled |
| 26 |
and libfoo-1.1 is removed. An emerge clean after the upgrade to libfoo-1.1 |
| 27 |
would have stopped this. This is so the reason that emerge now performs an |
| 28 |
autoclean. |
| 29 |
|
| 30 |
Paul |
| 31 |
|
| 32 |
-- |
| 33 |
Paul de Vrieze |
| 34 |
Junior Researcher |
| 35 |
Mail: pauldv@××××××.nl |
| 36 |
Homepage: http://www.cs.kun.nl/~pauldv |
Archives