| 1 |
thank you all guys !!! |
| 2 |
I understand now the complex resons to always have backups and test servers ;;;; |
| 3 |
I am sorry to make such a mess at the list, it wasn´t my intantion, |
| 4 |
thank one more time for the attention that was spend on my trouble. I |
| 5 |
promise that in the next time I will make some more relevant posts. |
| 6 |
|
| 7 |
|
| 8 |
On 10/22/05, Holly Bostick <motub@××××××.nl> wrote: |
| 9 |
> Hemmann, Volker Armin schreef: |
| 10 |
> > direct experience. I have seen xine and mplayer break multiple times |
| 11 |
> > or KDE loosing its themes, |
| 12 |
> |
| 13 |
> Yeah, but mplayer breaks if your breathe on it too hard, and Xine is not |
| 14 |
> all that much better (though better than gstreamer, and overall the best |
| 15 |
> in terms of stability). |
| 16 |
> |
| 17 |
> New releases of KDE often are so buggy that you 1) *have* to upgrade |
| 18 |
> whatever is available to get the bugfixes and 2) can't really be certain |
| 19 |
> that any breakage is related to library updates (or worse yet, only |
| 20 |
> *partial* library updates, not all relevant libraries, because all |
| 21 |
> relevant libraries don't necessarily have updates available at the same |
| 22 |
> time), rather than just one of the bugs. |
| 23 |
> |
| 24 |
> 'Loosing its themes' I've never seen (but then again I try to avoid |
| 25 |
> using KDE as much as possible), but of all the things that KDE might |
| 26 |
> (and has, in my experience) lose after a full, partial, or deep upgrade, |
| 27 |
> "themes" are about the last on my "oh, no, I'm now hysterical" list. But |
| 28 |
> that's just me. |
| 29 |
> |
| 30 |
> > because of qt updates or wesnoth. And that are the ones I remember |
| 31 |
> > without to much brain work. That is why I am healed from --deep |
| 32 |
> > updates |
| 33 |
> |
| 34 |
> OK. It's your box. |
| 35 |
> |
| 36 |
> In my opinion, it's impossible to avoid stuff breaking (on a |
| 37 |
> Gentoo/source-based distro) box; libraries and applications depending on |
| 38 |
> those libraries are *going* to be mis-matched at some point or another, |
| 39 |
> sometimes quite often. It's usually temporary, and usually easy to fix: |
| 40 |
> recompile the app against the updated library, as I did yesterday for |
| 41 |
> Beagle, or run <name_your_language>.updater-- I just found there's an |
| 42 |
> ocaml-updater script; who knew? or run the config utility for gcc, or |
| 43 |
> java or whatever is the problem today. Or switch apps, which is a |
| 44 |
> little-thought-of but often quite effective solution. Helps to be a bit |
| 45 |
> flexible, though, of course, which everybody does not have the liberty |
| 46 |
> to be. But if not, then just stick with stable and don't upgrade at all, |
| 47 |
> --deep or otherwise. |
| 48 |
> |
| 49 |
> Holly |
| 50 |
> |
| 51 |
> |
| 52 |
> -- |
| 53 |
> gentoo-user@g.o mailing list |
| 54 |
> |
| 55 |
> |
| 56 |
|
| 57 |
-- |
| 58 |
gentoo-user@g.o mailing list |
Archives